[01:00] <Eickmeyer> OvenWerks: It was really good timing to remove ladish and get raysession in with the python 2 removal.
[01:13] <OvenWerks> Eickmeyer: I am not sure if the Ardour problem is with waf or with the startup script.
[01:13] <OvenWerks> startup seems to be bash
[01:14] <OvenWerks> I just remember someone talking about it
[01:14] <OvenWerks> Arch if I recall correctly
[01:16] <OvenWerks> https://tracker.ardour.org/view.php?id=7796
[01:16] <OvenWerks> Eickmeyer: ^^
[01:18] <Eickmeyer> OvenWerks: Ardour isn't even affected per https://people.canonical.com/~ubuntu-archive/transitions/html/python2-rm.html
[01:20] <OvenWerks> a2jmidid
[01:21] <Eickmeyer> Who develops that?
[01:25] <OvenWerks> last copyright is 2008
[01:27] <OvenWerks> the Downloaded from url (http://home.gna.org/a2jmidid/) shows: The requested URL /a2jmidid/ was not found on this server.
[01:28] <OvenWerks> It seems to have been moved to https://repo.or.cz/a2jmidid.git
[01:30] <Eickmeyer> Well, that's a situation where it needs to be ported.
[01:33] <OvenWerks> The a2j code was added into jackd1 but not jackd2 last I heard
[01:33] <OvenWerks> (the same can be said for zita-ajbridge)
[01:35] <OvenWerks> 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] <OvenWerks> 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] <Eickmeyer> Yeah, I know. :/
[01:52] <OvenWerks> When are they killing pythin 2? before or after the LTS?
[01:53] <Eickmeyer> I'm not 100% sure.
[01:54] <Eickmeyer> Looks like before the LTS: https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Debian-Python-2-Process
[01:56] <Eickmeyer> I don't think Filipe is willing to let that functionality disappear.
[01:57] <OvenWerks> is there a python 4 to worry about
[01:57] <Eickmeyer> If it's in development, it hasn't been released.
[01:57] <OvenWerks> good
[05:07] <OvenWerks> 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] <OvenWerks> Eickmeyer: when you have a chance, can you post the url for: cat /proc/asound/PCH/codec#0 |pastebinit
[14:26] <Eickmeyer> OvenWerks: No such file or directory
[14:26] <Eickmeyer> (I don't have PCH)
[14:28] <Eickmeyer> This is ls /proc/asound https://paste.ubuntu.com/p/dgQj8THffh/
 *salts @Eickmeyer* you do read the ubuntu-devel lists right?
[14:41] <Eickmeyer> teward: I did not. I'll check my spam folder.
[14:42] <Eickmeyer> @teward001: Are you talking about vorlon's post?
 re: 32bit libs and such, mostly which packages need to be supported for things in the long term for 20.04
 yep
 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] <Eickmeyer> @teward001: Yeah, the ones I was concerned with are covered in that list. (carla/wine)
 cool
[14:58] <OvenWerks> Eickmeyer: maybe ls /proc/asound/card*/ though I expect cat /proc/asound/Generic/codec#0 might work... unless you have an ac97
[14:58] <OvenWerks> hmm, I may have to learn some other way of dealing with things.
[14:58] <Eickmeyer> https://paste.ubuntu.com/p/V3JGRVTbJv/
[14:58] <Eickmeyer> (codec#0)
[15:02] <OvenWerks> Thats an HDA style file
[15:10] <OvenWerks> Eickmeyer: you may note that the "Default PCM" has 44k1 48k 96k and 192k
[15:11] <OvenWerks> what is interesting is that none of your actual devices seem to support that list.
[15:11] <Eickmeyer> Yeah. I don't have my interface hooked-up right now.
[15:12] <OvenWerks> You analog devices (in and out) seem only to support 44k1 and 48k
[15:12] <Eickmeyer> That would be correct, afaik.
[15:12] <OvenWerks>  while your digital device suports 44100 48000 88200 96000 192000
[15:13] <OvenWerks> nope Im wrong, your inputs do support the default 44100 48000 96000 192000
[15:13] <OvenWerks>  so you can record at a higher SR that playback
[15:37] <Eickmeyer> Interesting. TIL
[15:37] <Eickmeyer> (today I learned)
[15:44] <OvenWerks> 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] <OvenWerks> except A&H's new mixer is 96k only :P
[15:48] <OvenWerks> (a cost saving deal as they run their eq at 96000 I am sure)
[15:52] <OvenWerks> 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] <OvenWerks> I know of devices that are 44k1 only, 32k and below, 48k only and 96k only
[15:54] <OvenWerks> however, all hda (internal) devices support at least 48k
[15:55] <OvenWerks> all other weird rate devices seem to be USB.
[15:57] <OvenWerks> I also know that the 48k only HDA devices I know about will open at 44k1  (laptop mics)
[15:59] <OvenWerks> Eickmeyer: I think I will set 48k for anything not USB that zita-ajbridge is using.
[16:00] <OvenWerks> 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] <OvenWerks> Eickmeyer: USB devices always seem to make a proper rates list, so use the closest available rate for that.
[16:02] <OvenWerks> Eickmeyer: does that make sense?
[16:02] <Eickmeyer> Yes, totally. 
[16:03] <OvenWerks> I think SRC would take away any advantage of using a higher rate than 48k in any case
[19:44] <OvenWerks> Eickmeyer: log rotate should wait for next cycle I think. 
[19:45] <Eickmeyer> Ok, that's fair.
[20:15] <OvenWerks> Eickmeyer: new controls is building for auto builds
[20:15] <Eickmeyer> Ok
[21:47] <Eickmeyer> OvenWerks: It builds, need release and backport?
[21:52] <OvenWerks> Eickmeyer: ok I downloaed it from autobuilds and installed and it seems to work for me so I guess it is releaseable.
[21:52] <Eickmeyer> Ok. I
[21:52] <Eickmeyer> I'll go ahead and push it to Eoan and backports.
[22:43] <OvenWerks> Thank you
[22:49] <OvenWerks> 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] <OvenWerks> Yup, they are all in there.