[10:32] <zmagii> Which software on Ubuntu Studio is used for Software Defined Radio, SDR?
[11:35] <narsiteo[m]> No idea
[12:11] <tarzeau> zmagii: i don't know how sdr stuff fits ubuntu studio?
[12:11] <tarzeau> zmagii: are you looking for something specific about sdr?
[12:49] <zmagii> Well, just was wondering if there is a default program that can do software defined radio.
[12:51] <zmagii> Maybe I should just try GNU radio.
[12:56] <tarzeau> yeah, there's some more generic ones, and there's specific stuff like dump1090, hacktv, welle.io, rtl-433...
[13:08] <zmagii> tarzeau: Alright, thanks.
[13:30] <wonko> SUCCESS!!!!!!!!!!!!!!!!!!!!
[13:30] <wonko> OvenWerks: Just put firmware version 4.8 on the AF4 and I'm now running 32/2
[13:34] <wonko> and now I'm running at 16/2
[15:16] <wonko> ok, 2 xruns so far at 16/2
[15:17] <wonko> maybe set that to 16/3
[15:17] <wonko> of course that may have been software starting
[15:17] <wonko> so I'll leave it as is for now
[17:06] <resd[m]> I just installed US 20.10 and now i can't get the UI opened for eq10q
[17:06] <resd[m]> anyone else had this problem?
[17:37] <wonko> OvenWerks: dammit I rebooted now it won't start anymore :(
[17:37] <wonko> actually, now it's back to doing the unhandled xrun thing
[17:38] <OvenWerks> resd[m]: are you using it as a plugin? (I am tryig to remember if there is a jack client version) and which program are you using as a host?
[17:38] <resd[m]> OvenWerks:  Ardour
[17:38] <wonko> I set threadirqs this time. Please don't tell me that's making it worse. :)
[17:39] <OvenWerks> resd[m]: I would have to be at a machine that has 20.10 on it. I can check tomorrow...
[17:40] <resd[m]> cool
[17:40] <resd[m]> Is it possible to launch it from terminal to get error messages/
[17:40] <resd[m]> ?
[17:47] <OvenWerks> wonko: I don't think I set threadirqs. Do you have more than one thread per core?
[17:48] <OvenWerks> resd[m]: it seems it is a plugin only. The gui works fine in 20.04 though
[17:48] <OvenWerks> resd[m]: you can launch Ardour from terminal though
[17:50] <wonko> OvenWerks: so yeah, enabling threadirqs (at least with Liquorix) makes it not work. Keeping that disabled and it starts right up without issue.
[17:50] <wonko> I'll try the stock 5.4-lowlatency kernel later
[17:51] <OvenWerks> resd[m]: are you using ardour from ubuntu or from ardour.org?
[17:52] <wonko> OvenWerks: how do I check threads/queue?
[17:52] <wonko> oh, you mean CPU config
[17:52] <wonko> yeah, it's 6C/12T
[17:52] <OvenWerks> when starting from commandline, the repo version is lower case and the ardour.org version is uppercase A
[17:54] <OvenWerks> I have found in the past... when I still had a cpu with hyperthread, that at low latency (below 64/2) turning HT off cleaned up xruns
[17:54] <OvenWerks> That was a long time ago (P4) and I bought an i5 4c4t for that reason
[17:55] <OvenWerks> so I have not tested that since
[17:56] <OvenWerks> wonko: as you go for lower latency, system setup becomes more critical :) I have also found that stopping crond makes a difference
[17:57] <OvenWerks> (though the AF12 seemed to do 16/2 for more than 24 hrs with no xruns and crond on)
[17:58] <OvenWerks> crond runs at nice=10 but if it is doing network/disk actions with large data chunks, the network/disk access is still atomic
[18:08] <wonko> I only seem to get xruns when an app misbehaves
[18:09] <wonko> GoLand was being quite dumb (A reboot fixed that, btw)
[18:09] <wonko> Also, it's completely unfair to compare AMD HT with Intel HT and even current HT with the older HT stuff intel was doing.
[18:09] <wonko> The pre-core implementation was very, very bad
[18:16] <OvenWerks> wonko: that is why I made sure to tell you what I did my testing on and to state I have not done any testing on newer HW
[18:17] <wonko> I'm just curious why threadirqs makes a mess of everything
[18:17] <wonko> that seems odd to me
[18:17] <wonko> ooohhhhhhh
[18:18] <wonko> "Liquorix kernels are built with CONFIG_IRQ_FORCED_THREADING=y so the threadirqs kernel parameter is not needed"
[18:18] <wonko> I wonder if adding it a "second time" causes issues
[18:18] <OvenWerks> wonko: I think the Linux kernel has improved as well. At the time the kernel treated each HW thread as a core, but I think now it will not run a low latency thread or maybe any thread on the second thread if a process has high enough priority
[18:19] <OvenWerks> wonko: maybe a second use toggles it
[18:19] <wonko> that could be
[18:20] <wonko> the only "oddidty" is /etc/init.d/rtirq status output looks like threadirqs isn't active
[18:20] <wonko> well, whatever
[18:20] <wonko> it works
[18:20] <OvenWerks> :)
[18:20] <wonko> I'll try to not overthink it. :-D
[18:22] <wonko> I will put my efforts back into this work nonsense instead. :-D
[19:28] <sirriffsalot> I can see that Carla scanned a VST that I wanted to try, installed it with experimental features (wine etc) and everything went fine. But when I search for it after having refreshed and scanned, it doesn't show up in the list..?
[19:29] <sirriffsalot> But if I just drag the .dll plugin file into carla and drop it, it works.. lol
[21:26] <Sbur3> How do I get rid of one source ppa for Mixxx
[21:37] <guiverc> Sbur3, it sounds like you're asking to use ppa-purge; https://wiki.ubuntu.com/FocalFossa/ReleaseNotes/UbuntuStudio has an example of it's use
[22:29] <wonko> OvenWerks: off running my wife to a dr appt so music paused, screensaver going and........ 4 xruns. I'm thinking that for any serious music purposes I might have to follow you recommendation to literally shut down everything I don't need. :)