[00:29] <Tode_I> Anyone know how to unlearn a CC control mapping in Zyn Fusion?
[00:35] <Eickmeyer> Tode_I: I don't know (not a keyboard player), but you can try asking in #lad. The developer hangs out in there often.
[00:37] <Tode_I> lad you say? Merci!
[13:21] <wonko> OvenWerks: Another jack crash, dammit!
[13:22] <wonko> http://paste.ubuntu.com/p/2vpGYSDFX7/
[13:23] <wonko> The last two days worth of logs
[15:30] <mrz80> wonko:   Just off the cuff, one thing that jumps out at me is  1m[31mERROR: Cannot lock down 82280346 byte memory area (Cannot allocate memory)[0m  pretty much as soon as jackd starts.
[15:31] <mrz80> I've seen some discussion threads about running configured for unlimited memory allocation
[15:32] <mrz80> Maybe try configuring jackd to run with no memory lock?
[15:45] <wonko> Any idea how I do that? 😁
[15:50] <mrz80> If you're running qjackctl, select setup, then go to the advanced tab under settings
[15:50] <mrz80> There's an option there for running with no memory lock
[15:50] <wonko> I'm using ubuntustudio-controls, let me check what options it has
[15:51] <wonko> doesn't look like a settable option there
[15:57] <mrz80> hmm...
[16:04]  * OvenWerks notes that jack does not fail to start or run, meaning that memory locking is unlikely to be the problem
[16:05] <wonko> what's the exact issue then with the memory?
[16:05] <wonko> or is it just a harmless warning?
[16:05] <OvenWerks> earlier work showed that the usb device was doing odd reconnects
[16:06] <wonko> is there something I can maybe be watching (system level) to see what's up with that?
[16:07] <OvenWerks> If the reconnects were quick, things recovered. if not jack would eventually crash
[16:08] <OvenWerks> wonko: ls /etc/seccurity/limits.d/
[16:08] <OvenWerks> should show audio.conf
[16:08] <wonko> is this meaningful?
[16:08] <wonko> [116257.414153] xhci_hcd 0000:81:00.0: WARN Event TRB for slot 7 ep 12 with no TDs queued?
[16:09] <wonko> yes, I see audio.conf
[16:09] <OvenWerks> possibly
[16:09] <wonko> 81:00.00 is the usb card the audio device is plugged inot
[16:09] <wonko> into
[16:10] <wonko> @audio   -  rtprio     95
[16:10] <wonko> @audio   -  memlock    unlimited
[16:10] <wonko> #@audio   -  nice      -19
[16:10] <wonko> is the contents of audio.conf
[16:10] <OvenWerks> I thought that would be the case, so far as I know when you start -controls it has no red warning at the top and it test mem locking.
[16:10] <OvenWerks> right, that makes sense
[16:11] <OvenWerks> I don't know what the xhci error means though
[16:11] <wonko> i'm googling now. :)
[16:12] <OvenWerks> But before I changed -controls we were seeing the same usb box was sending device connects more than once.
[16:18] <wonko> ok, red herring it seems
[16:18] <wonko> maybe
[16:18] <wonko> it's hard to say
[16:18] <wonko> everything pertaining to that message is years old
[16:18] <wonko> in a much older kernel
[16:19] <OvenWerks> which device (USB) do you have a gain?
[16:19] <OvenWerks> *again
[16:32] <wonko> MiDiPLUS AKM320, Korg nanoKONTROL2, Native Instruments Komplete Audio 6 Mk2, Logitech webcam, Das Keyboard and Logitech M705
[16:32] <wonko> also, seems like Asus just released a new BIOS for this motherboard (more than 2 years after the last bios version!)
[16:32] <wonko> so I'm also going to try that.
[16:49] <OvenWerks> how about that, my $0.01 audio interface sounds better than my $0.68 audio interface  :)
[16:52] <OvenWerks> using input only, so I don't know how the output sounds. The 68 cent one had a higher frequency buzz (power supply noise?) but the 1 cent one doesn't.
[16:55] <OvenWerks> I am using it for guitar input and find that computer mics are wired oddly. They are trs and I have to pull the plug out so my plugs tip matched the socket ring. I also notice noises that indicate there is dc on the input (scratchy controls, loud clicks when plugging) so a blocking cap would be in order.
[17:03] <OvenWerks> also to note I am running them at 128/2 which may be below design limits ...
[18:33] <Eickmeyer> wonko, OvenWerks: The memory allocation issue is an issue with systemd that was fixed in the verion in 19.10, so I highly suggest the beta at this point.
[18:33]  * Eickmeyer is working on all sorts of blog post stuff at this point.
[18:34] <OvenWerks> something like that had crossed my mind. Good to know.
[18:35] <Eickmeyer> I'm also going to be going hardcore on release notes.
[18:36] <OvenWerks> However, my gut feeling with the above problem is an under powered usb box.
[18:36] <Eickmeyer> Very well possible.
[18:39] <wonko> Well I updated my BIOS now my computer won't boot. Yay!
[18:39] <Eickmeyer> Oof
[18:51] <OvenWerks> wonko: can you enter the bios? maybe enter and safe bios and try.
[18:52] <OvenWerks> may have to reset to default... or reset things up or whatever bcause the the place the bios stores it's variables may have reordered or something.
[18:52] <OvenWerks> s/safe/save/
[19:05] <wonko> Looks like the update set things back to default
[19:05] <wonko> So it's trying to legacy boot a uefi system
[19:05] <wonko> Is my theory anyway
[19:05] <wonko> 🤣
[19:06] <wonko> Yep, that was it
[19:11] <wonko> Well, now on to the next issue. Stuck at the grub splash screen after hitting boot on the default option.
[19:12] <wonko> Oh, whole thing was locked up. Had to hit the reset button.
[19:20] <wonko> And booting
[20:30] <wonko> OvenWerks: It I turn boost back on the cpu temps hit 69C and 83C