[01:00] <MaynardWaters> hi jasonerid[m]
[01:05] <tomreyn> jasonerid[m]: hi. it's nice that you said hello, but note that it's common to just ask your question(s) and to provide details (use a pastebin for 2+ lines of output), no need to for others to reply to start discussing it.
[01:06] <OvenWerks> :)
[01:06] <OvenWerks> I think he was going to say the same thing
[01:08] <tomreyn> nothing was said for 5 minutes so i though i'd point it out,
[14:31] <wonko> OvenWerks: Do you know where I can find a list of FW chipsets that are going to work? I'm looking at the StarTech ones with the TI chips but I want to make sure they will work solidly. Also, I want to see if it's worth spending a bit more on the newer chipset or not. (TSB82AA2 vs XIO2213B)
[14:32] <wonko> I don't need 800 nor do I need 3 ports so the only reason to but the XIO2213B based card would be the chipset is better.
[14:32] <wonko> s/but/buy/
[15:15] <tha0leman> moin
[16:09] <inviolato> Salve a tutti
[16:10] <inviolato> Siccome vengo da anni di  windows
[16:11] <inviolato> Vorrei sapere come va ubuntu studio....
[16:13] <inviolato> Mi dite come va ubuntu studio ???
[16:14] <inviolato> C'e' nessuno ???
[16:16] <inviolato> Vorrei mettere ubuntu studio su un ssd
[16:16] <inviolato> Ma ho usao sempre windows.....
[16:18] <inviolato> Ubuntu studio is good ???
[16:19] <inviolato> I have usad only windows...
[17:41] <wonko> $24 XIO2213B card. Worth a shot. :-D
[18:22] <belthesar[m]> Heya folks - upon upgrading to the new Studio Controls on Pop_OS! 20.10, it's failing to launch with `SystemError: ffi_prep_closure(): bad user_data (it seems that the version of the libffi library seen at runtime is different from the 'ffi.h' file seen at compile-time)`. I've been having trouble tracing down which library I need to upgrade/downgrade, whether it's a library itself or the python package, and if so,
[18:22] <belthesar[m]> if there's an python environment I should be doing that in. Any suggestions would be helpful. Thanks!
[18:33] <OvenWerks> wonko: there used to be a page with chip numbers but I can't find it right now, just this: http://ffado.org/info/faq/faq-04-firewire-02-controller/
[18:34] <wonko> yeah, that list is "hasn't been moved over yet"
[18:34] <wonko> which is a little annoying
[18:35] <wonko> Hmm, so sounds like I may have made the wrong choice. :)
[18:35] <OvenWerks> wonko: I think this is the page I had before: http://subversion.ffado.org/wiki/HostControllers
[18:36] <wonko> "These are known to work very well with single audio devices and also with two or more audio devices aggregated on the same bus. Therefore these controllers can generally be recommended for use with FFADO."
[18:36] <wonko> ok, maybe not (I got an XIO card)
[18:36] <OvenWerks> it says all xi0 chips sets
[18:37] <wonko> well, i'll let you know after everything arrives. :)
[18:37] <OvenWerks> I am pretty sure mine is an xio
[18:38] <wonko> The card should be here monday. No idea how long I'll have to wait for the AudioFire. Tracking info is available soon hopefully.
[18:38] <OvenWerks> I also have a VIA or two because things did not work at first... it turns out it was the cable. I found the 800-400 cable worked but the 400-400 did not. It may have been just a bad cable though
[18:39] <wonko> I thought VIA were supposed to be the problematic ones?
[18:39] <wonko> One of the reasons I focused on the TI chipsets
[18:41] <OvenWerks> they are problematic if you have more than one fw audio device chained... but to be honest, I have not had one of my via chipset cards work because the cable is bad
[18:42] <OvenWerks> my audiofire has two FW ports so one in and one out. The TI is the best chipset to get in any case I think. That is what I am using.
[18:42] <wonko> at $24 I'm certainly not complaining about having to go that route. :)
[18:45] <OvenWerks> belthesar[m]: it sounds like the libffi nees to be down graded. The python jack package seems not to have been upgraded yet. so maybe a bug report. We have seen this off and on and it seems to most times last a day or so until the packages are fixed.
[18:46] <belthesar[m]> <OvenWerks "belthesar: it sounds like the li"> Thanks, OvenWerks
[18:47] <wonko> OvenWerks: Opinion on 20.04 vs 20.10 vs 21.04? (I'm assuming 21.04 will be out until I've moved and gotten a new computer)
[18:47] <wonko> I kinda want to stick with 20.04 for LiveUpdate but as I'll be on Zen3 I also want the latest things I can get.
[18:49] <belthesar[m]> Oh fun, looks like Ubuntu doesn't provide any different versions of libffi anything for 20.10 other than 3.4. Now, off to find the bug tracker.
[18:57] <belthesar[m]> The LaunchPad bug tracker looks pretty abandoned, and poking around on ubuntustudio.org didn't lead me to anything in particular. Am I in the right spot, or is there another place to go for bug reports?
[18:58] <belthesar[m]> Ahh, sorry, ignore me. Looks like I just needed to poke around a bit more on Launchpad. Apologies, I'm not super well versed there.
[19:00] <wonko> Launchpad is..... not great. :-D
[19:01] <belthesar[m]> It does look like the `studio-controls` repo isn't configured to send alerts to devs there though. Is the accepted pattern to send bugs for project repos to the project?
[19:01] <OvenWerks> belthesar[m]: the bug would be with the python3-jack-client
[19:01] <OvenWerks> the problem is not with studio-controls
[19:01] <belthesar[m]> Ahh, thanks again for pointing me in the right direction.
[19:01] <OvenWerks> the package probably just needs a rebuild
[19:03] <OvenWerks> looking at https://packages.ubuntu.com/groovy/python3-jack-client
[19:04] <OvenWerks> it looks like the python3-jack-clienthas bigger problems
[19:10] <belthesar[m]> Exciting. /s Oh well, I suppose I'll just keep qjackctl running and such while I need it in the interim. Thanks again for all the legwork, OvenWerks, and to the team. Big exciting changes y'all are doing.
[19:13]  * OvenWerks is going to have to install 20.10 so he can put a bug report
[19:13] <OvenWerks> it works fine in 20.04
[19:14] <belthesar[m]> I'm happy to fill out a report. Still checking to see what version of python3-jack-client is provided on 20.04
[19:15] <belthesar[m]> Weird, it's the same version.
[19:17] <belthesar[m]> It looks like upstream Debian is running 0.5.2. I'm poking around to see if any fixes were mentioned, but not seeing anything quite yet on the Github repo
[19:19] <belthesar[m]> Oh, well this might be a me thing. I have a different of that library in my .local user packages @ 0.5.3.
[19:20] <belthesar[m]> Nah, I'm getting the same thing with the `dist-packages` version. Worth a shot.
[19:35] <OvenWerks> that ouwld be the problem then it is the same version but it needs to be updated. It seems the packages it depends on do not exist. Probably they are called a different name or something
[19:36] <OvenWerks> belthesar[m]: do you have python3-cffi-backend installed?
[19:37] <belthesar[m]> I do @ 1.14.2-1
[19:39] <OvenWerks> it is funny that 20.04 shows packages not available too but seems to work.
[19:40] <belthesar[m]> Same w/ upstream Debian.
[19:40] <belthesar[m]> At least, wrt packages not available
[19:48] <OvenWerks> ya but python3-cffi-backend "provides" those packages
[19:48] <OvenWerks> so that is not the problem
[19:48] <OvenWerks> it probably just needs to be repackaged which should happen if a bug report goes in
[19:49] <OvenWerks> python3-jack-client is probably not a much used package
[19:54] <OvenWerks> belthesar[m]: you might try the python3-jack-client for 21.04
[19:55] <belthesar[m]> Mmm, yeah, that's not a bad idea. I'll try adding the repo for it in a sec here.
[19:55] <belthesar[m]> I had a very nice bug report in, and then my caching DNS server decided to burp and the form wasn't saved.
[19:55] <belthesar[m]> I'll.. get back to it after food. 😅
[19:57] <belthesar[m]> No such luck wrt python3-jack-client 0.5.2 from the 21.04 repo
[19:58] <belthesar[m]> I'm about to grab source and compile it myself
[19:58] <OvenWerks> it appears that the one from 21.04 may work for 20.10 but not for 21.04 there seems to be no link to rebuild python3-jack-client if it depends are rebuilt
[19:58] <OvenWerks> belthesar[m]: it may be au upstream problem then
[20:01] <belthesar[m]> Yeah, quite possible. When I tried looking at this after the upgrade, I did end up trying to use the latest python3 jack client from PyPI, and it threw the same error.
[20:13] <OvenWerks> let us know how the comile goes.
[20:13] <OvenWerks> if that works good we can repackage if not it is upstream
[20:13] <OvenWerks> we may patch
[20:14] <belthesar[m]> Yeah, 100% an upstream problem. Getting the same thing when running from Git. Looks like that's the place to put in a bug report. I don't seem to be getting a good compile though, per se, as much as just running the local version. I'm admittedly pretty new to python dealing with ffi.
[20:14] <belthesar[m]> I'm gonna poke at it a bit more.
[20:14]  * OvenWerks is out to lunch...
[20:17] <belthesar[m]> At this point, I'm wondering if it's not JACK-Client as much as it's the cffi module.
[20:22] <belthesar[m]> Got it. It's 100% `cffi`. Compiling from source and loading has me running again.
[20:46] <chris_uk[m]> Greetings. My Ubuntu Studio 20.04 just had an upgrade of Studio Controls and now there is no sound coming from my Focusrite 6i6 2nd gen. I had a look at the various options in studio controls and can' t see anything amiss. Any ideas?
[20:49] <chris_uk[m]> Ignore last message. Problem solved. Not sure how. Just poked around a bit. Lol.
[20:56] <chris_uk[m]> Another problem: sound plays OK now using Firefox at e.g. YouTube. But if I launch the Pulse Audio mixer from top right of desktop during music playback, the audio momentarily stops and when it returns the speed is slightly slower with a lower pitch.
[21:03] <chris_uk[m]> My audio settings.
[21:24] <belthesar[m]> That sounds like sample rate issues, chris_uk
[21:38] <chris_uk[m]> The Jack sample rate is set at 48KHz.
[21:53] <OvenWerks> chris_uk[m]: wierd. I have never had that.
[21:54] <OvenWerks> I am pretty sure the fucusrite handles 48k just fine
[21:58] <OvenWerks> belthesar[m]: the cffi you complied, was that from git? is it the release or master?
[21:59] <OvenWerks> chris_uk[m]: I guess I should also ask which rate is right? :)
[22:00] <belthesar[m]> I had to compile from source (https://foss.heptapod.net/pypy/cffi/. I pulled straight from default (master), not the release version.
[22:00] <belthesar[m]> If you want, I can easily switch branches and try it again.
[22:00] <belthesar[m]> They do have 1.14 tagged.
[22:01] <belthesar[m]> The fact that I have to relearn mercurial after not touching it for 7 years is fun though.
[22:03] <belthesar[m]> Yeah, switched to release version, and ran it. I think it has to be that I have the latest libffi headers.
[22:17] <chris_uk[m]> OvenWerksThe original audio sounds right before the slowdown which is definately slower than it ought to be.
[22:21] <chris_uk[m]> The Focusrite has been fine up to now. I haven' t changed its internal sample rate which was set at 48 kHz. I would have to boot it into a Windows system to verify that though as the Focusrite controls software doesn't run in Linux.
[22:22] <OvenWerks> on the pulseaudio mixer, does it show any devices under the configuration tab?
[22:22] <OvenWerks> (if you use 48k all the time you may wish to change the pulseaudio default from 44k1 to 48k)
[22:28] <inviolato> Salve a tutti
[22:28] <chris_uk[m]> OvenWerks  Yes, the Focusrite is listed and also HP107GL HD audio controller, whatever that is. In the Focusrite drop down menu, I can select various outputs like 2.1 (currently selected) and 5.1 etc. Can' t see where to set the pulse audio sample rate.
[22:30] <chris_uk[m]> 2.1 plus multichannel input
[22:32] <chris_uk[m]> The other audio controller is off (no profile selected).
[22:32] <OvenWerks> chris_uk[m]: /etc/pulse/daemon.conf
[22:32] <chris_uk[m]> Ok
[22:33] <OvenWerks> there is a place that can be put in the home directory as well if you don't want to change the system default.
[22:33] <OvenWerks> I thought I had seen it in more places
[22:34] <OvenWerks> you do have to take the ; out of the front of the line, normally I copy the line first then remove the ; and edit that line so I have:
[22:34] <OvenWerks> ; default-sample-rate = 44100
[22:35] <OvenWerks> default-sample-rate = 48000
[22:35] <OvenWerks> alternate-sample-rate = 48000
[22:35] <chris_uk[m]> Default sample rate us 41.1 kHz. Alternate is 48. So set both to 48?
[22:35] <OvenWerks> yeah
[22:36] <OvenWerks> that way pulse will not change the rate based on what the app asks for and the app will do src
[22:36] <OvenWerks> (actually, I run jack all the time so pulse only sees jack and no devices  :)  )
[22:37] <chris_uk[m]> Ok
[22:39] <chris_uk[m]> So no semi colons except for first sample rate line?
[22:39] <OvenWerks> yup, ; means ignore the rest of this line
[22:39] <OvenWerks> (comment)
[22:41] <OvenWerks> if you leave the alt commented out Pulse will make it 44k1 if default is 48k
[22:41]  * OvenWerks had a laptop where the internal mic was 48k only
[22:42] <chris_uk[m]> Understood. Thanks.
[22:43] <chris_uk[m]> Permission denied when I try to save the document.
[22:43] <OvenWerks> sudo nano filename
[22:43] <OvenWerks> yes you have to be root to edit that one
[22:44] <chris_uk[m]> Dont understand? Do it through terminal?
[22:44] <OvenWerks> sudo nano /etc/pulse/daemon.conf
[22:44] <OvenWerks> yes in a terminal
[22:44] <chris_uk[m]> Ok
[22:45] <OvenWerks> it will ask for your password
[22:51] <chris_uk[m]> How do I save the document in terminal?
[23:00] <chris_uk[m]> Ok, I found out! Done
[23:04] <chris_uk[m]> Bingo! Works fine now. No change of sample rate when I launch mixer. Many thanks!