[01:00] OvenWerks: It was really good timing to remove ladish and get raysession in with the python 2 removal. [01:13] Eickmeyer: I am not sure if the Ardour problem is with waf or with the startup script. [01:13] startup seems to be bash [01:14] I just remember someone talking about it [01:14] Arch if I recall correctly [01:16] https://tracker.ardour.org/view.php?id=7796 [01:16] Eickmeyer: ^^ [01:18] OvenWerks: Ardour isn't even affected per https://people.canonical.com/~ubuntu-archive/transitions/html/python2-rm.html [01:20] a2jmidid [01:21] Who develops that? [01:25] last copyright is 2008 [01:27] the Downloaded from url (http://home.gna.org/a2jmidid/) shows: The requested URL /a2jmidid/ was not found on this server. [01:28] It seems to have been moved to https://repo.or.cz/a2jmidid.git [01:30] Well, that's a situation where it needs to be ported. [01:33] The a2j code was added into jackd1 but not jackd2 last I heard [01:33] (the same can be said for zita-ajbridge) [01:35] Filipe's plan, to the best of my knowledge, was to bring jackd2 to the point of compatablilty with jackd1 and then retire jackd1 [01:36] However, Filipe is a busy man. There has not been a kxstudio iso release for 5 years or so (last was based on 14.04) and he is back working with MOD [01:51] Yeah, I know. :/ [01:52] When are they killing pythin 2? before or after the LTS? [01:53] I'm not 100% sure. [01:54] Looks like before the LTS: https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Python-2-Process [01:56] I don't think Filipe is willing to let that functionality disappear. [01:57] is there a python 4 to worry about [01:57] If it's in development, it hasn't been released. [01:57] good [05:07] yuck! I get a whole pile of lines with Rates: for my internal (PCH) card... it appears some of them are the standard HAD rates that the hda bus will handle and the others are what the device actually handles :P [05:08] Eickmeyer: when you have a chance, can you post the url for: cat /proc/asound/PCH/codec#0 |pastebinit [14:26] OvenWerks: No such file or directory [14:26] (I don't have PCH) [14:28] This is ls /proc/asound https://paste.ubuntu.com/p/dgQj8THffh/ [14:40] *salts @Eickmeyer* you do read the ubuntu-devel lists right? [14:41] teward: I did not. I'll check my spam folder. [14:42] @teward001: Are you talking about vorlon's post? [14:42] re: 32bit libs and such, mostly which packages need to be supported for things in the long term for 20.04 [14:43] yep [14:43] since IIRC you said some 32bit things were still needed for things in Studio I was wondering if you put any input in yet 😛 [14:44] @teward001: Yeah, the ones I was concerned with are covered in that list. (carla/wine) [14:45] cool [14:58] Eickmeyer: maybe ls /proc/asound/card*/ though I expect cat /proc/asound/Generic/codec#0 might work... unless you have an ac97 [14:58] hmm, I may have to learn some other way of dealing with things. [14:58] https://paste.ubuntu.com/p/V3JGRVTbJv/ [14:58] (codec#0) [15:02] Thats an HDA style file [15:10] Eickmeyer: you may note that the "Default PCM" has 44k1 48k 96k and 192k [15:11] what is interesting is that none of your actual devices seem to support that list. [15:11] Yeah. I don't have my interface hooked-up right now. [15:12] You analog devices (in and out) seem only to support 44k1 and 48k [15:12] That would be correct, afaik. [15:12] while your digital device suports 44100 48000 88200 96000 192000 [15:13] nope Im wrong, your inputs do support the default 44100 48000 96000 192000 [15:13] so you can record at a higher SR that playback [15:37] Interesting. TIL [15:37] (today I learned) [15:44] I can't see that being a feature, so it must be cheaper (on board preamps being some of the worst) [15:46] * OvenWerks is temped to A) hack zita-ajbridge to do the selecting B) only look for 44k1 and 48k and lower in the list [15:47] except A&H's new mixer is 96k only :P [15:48] (a cost saving deal as they run their eq at 96000 I am sure) [15:52] Eickmeyer: thinking out loud here... I think I will blacklist 88k2 as one of the ones generally not supported. I think I can get away with black listing anything higher than 96k as well. [15:53] I know of devices that are 44k1 only, 32k and below, 48k only and 96k only [15:54] however, all hda (internal) devices support at least 48k [15:55] all other weird rate devices seem to be USB. [15:57] I also know that the 48k only HDA devices I know about will open at 44k1 (laptop mics) [15:59] Eickmeyer: I think I will set 48k for anything not USB that zita-ajbridge is using. [16:00] Eickmeyer: The jack master has feedback that it has not started though not why :) So the user can fiddle with that rate to their hearts content [16:01] Eickmeyer: USB devices always seem to make a proper rates list, so use the closest available rate for that. [16:02] Eickmeyer: does that make sense? [16:02] Yes, totally. [16:03] I think SRC would take away any advantage of using a higher rate than 48k in any case [19:44] Eickmeyer: log rotate should wait for next cycle I think. [19:45] Ok, that's fair. [20:15] Eickmeyer: new controls is building for auto builds [20:15] Ok [21:47] OvenWerks: It builds, need release and backport? [21:52] Eickmeyer: ok I downloaed it from autobuilds and installed and it seems to work for me so I guess it is releaseable. [21:52] Ok. I [21:52] I'll go ahead and push it to Eoan and backports. [22:43] Thank you [22:49] with regards to the "setting values for dummy and FW at startup" thing. I did check and autojack does not send those. I can only assume that once they have been set at any time (as I did while testing) the jack log shows reloading from the config file at each startup. [22:51] Yup, they are all in there.