=== tim is now known as Guest77923 [00:29] Anyone know how to unlearn a CC control mapping in Zyn Fusion? [00:35] 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] lad you say? Merci! [13:21] OvenWerks: Another jack crash, dammit! [13:22] http://paste.ubuntu.com/p/2vpGYSDFX7/ [13:23] The last two days worth of logs [15:30] 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] I've seen some discussion threads about running configured for unlimited memory allocation [15:32] Maybe try configuring jackd to run with no memory lock? [15:45] Any idea how I do that? 😁 [15:50] If you're running qjackctl, select setup, then go to the advanced tab under settings [15:50] There's an option there for running with no memory lock [15:50] I'm using ubuntustudio-controls, let me check what options it has [15:51] doesn't look like a settable option there [15:57] 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] what's the exact issue then with the memory? [16:05] or is it just a harmless warning? [16:05] earlier work showed that the usb device was doing odd reconnects [16:06] is there something I can maybe be watching (system level) to see what's up with that? [16:07] If the reconnects were quick, things recovered. if not jack would eventually crash [16:08] wonko: ls /etc/seccurity/limits.d/ [16:08] should show audio.conf [16:08] is this meaningful? [16:08] [116257.414153] xhci_hcd 0000:81:00.0: WARN Event TRB for slot 7 ep 12 with no TDs queued? [16:09] yes, I see audio.conf [16:09] possibly [16:09] 81:00.00 is the usb card the audio device is plugged inot [16:09] into [16:10] @audio - rtprio 95 [16:10] @audio - memlock unlimited [16:10] #@audio - nice -19 [16:10] is the contents of audio.conf [16:10] 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] right, that makes sense [16:11] I don't know what the xhci error means though [16:11] i'm googling now. :) [16:12] But before I changed -controls we were seeing the same usb box was sending device connects more than once. [16:18] ok, red herring it seems [16:18] maybe [16:18] it's hard to say [16:18] everything pertaining to that message is years old [16:18] in a much older kernel [16:19] which device (USB) do you have a gain? [16:19] *again [16:32] MiDiPLUS AKM320, Korg nanoKONTROL2, Native Instruments Komplete Audio 6 Mk2, Logitech webcam, Das Keyboard and Logitech M705 [16:32] also, seems like Asus just released a new BIOS for this motherboard (more than 2 years after the last bios version!) [16:32] so I'm also going to try that. [16:49] how about that, my $0.01 audio interface sounds better than my $0.68 audio interface :) [16:52] 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] 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] also to note I am running them at 128/2 which may be below design limits ... [18:33] 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] something like that had crossed my mind. Good to know. [18:35] I'm also going to be going hardcore on release notes. [18:36] However, my gut feeling with the above problem is an under powered usb box. [18:36] Very well possible. [18:39] Well I updated my BIOS now my computer won't boot. Yay! [18:39] Oof [18:51] wonko: can you enter the bios? maybe enter and safe bios and try. [18:52] 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] s/safe/save/ [19:05] Looks like the update set things back to default [19:05] So it's trying to legacy boot a uefi system [19:05] Is my theory anyway [19:05] 🤣 [19:06] Yep, that was it [19:11] Well, now on to the next issue. Stuck at the grub splash screen after hitting boot on the default option. [19:12] Oh, whole thing was locked up. Had to hit the reset button. [19:20] And booting [20:30] OvenWerks: It I turn boost back on the cpu temps hit 69C and 83C