[00:37] <OvenWerks> Ok, it seems the system sees PW's version of the libjack* stuff... this means jackd/jackdbus also sees the wrong lib. So this is a PW problem.
[15:49] <Eickmeyer> OvenWerks: That's all really interesting. Is wtay aware?
[16:10] <Eickmeyer> OvenWerks: On another note, I'm not sure what's going on, but the pulse bridges are no longer starting on 21.10 with the jack 1.9.17 from hirsute. I have the new 1.9.19 with fixes from falktx building now, so we'll see what happens.
[16:17] <Eickmeyer> OvenWerks: Ok, so in 21.10, pulseaudio is a user systemd process. Instead of pulseaudio --kill one should use systemctl --user [start/stop/restart] pulseaudio
[18:14] <OvenWerks> Eickmeyer: I did notice a norespawn thing in there
[18:14] <OvenWerks> This would make things work with cadence
[19:56] <OvenWerks> Eickmeyer: the thing is to make a new autojack still work older os.
[19:59] <OvenWerks> Eickmeyer:  my problem there is getting jackd to see the right libjack. exporting a corrected libpath (nopw_jack jackd -d alsa) does not seem to work.
[19:59] <OvenWerks> maybe I am doing someting wrong
[20:10] <Eickmeyer> OvenWerks: Don't know if you saw, but we're going to have the zalsa built-in client in jack, so that might help.
[20:17] <Eickmeyer> OvenWerks: Good news is that the crashes with jack are no longer an issue on 1.9.19 with the fixes I impemented from falktx. Bad news is that studio-controls no longer detects that jack is running.
[20:17] <Eickmeyer> (jack status is stopped, no update on DSP usage)
[20:17] <Eickmeyer> Even though I confirmed it is running via carla, qjackctl, etc.
[20:36] <Eickmeyer> OvenWerks: Disregard, it's fine after restarting autojack. ¯\_(ツ)_/¯
[21:44] <OvenWerks> Eickmeyer: zalsa built in... I have to experiment with. There are two issues I foresee... A) I don't think we can name them to something apropriate. B) I am not sure more than one can run at the same time.
[21:49] <OvenWerks> Eickmeyer: there are two other difficulties that may also arise. The load command seems to have no params for sample rate... some cards need that, there seems to be no parameter for periods or period size... if jack is set to 32, the extra device may need as high as 256 (more for hdmi)
[23:23] <Eickmeyer> OvenWerks: These things need to be communicated to falktx in #jack, #lad, or elsewhere.
[23:23] <Eickmeyer> This was his design.
[23:24] <Eickmeyer> I can potentially move the zalsa items to a new package.
[23:40] <OvenWerks> Eickmeyer: it does not matter if zalsa is included or not as zita-ajbridge will still work.
[23:41] <Eickmeyer> OvenWerks: Yeah, that's one reason why I don't know if, for our purposes, it's a big deal. Seems like a cool idea though.
[23:41] <OvenWerks> I will have to look at the code more closely to see if there are more parameters that have not been mentioned
[23:42] <OvenWerks> There are apparently a pile more dbus commands, queries and signals that are not documented such that I may not need to ever open a jack client.
[23:43] <OvenWerks> I have already moved xrun and DSP to dbus.
[23:43] <OvenWerks> I don't know how this will work with pipewire though