[16:24] Eickmeyer: playing with zita-njbridge. From a 20.04 machine to a 22.04 machine sound is fine. From 22.04 to 20.04 the sound is breaking up. no xruns on either end. The other day using pipewire, zita-njbridge is very unstable, crashes and doesn't seem to connect at all if it does run. So some work to do. I wonder is zita-* needs to be build using c99 ir c11 or some other switch. [16:26] OvenWerks: It's possible, I'd have to investigate debian/rules. [16:27] Eickmeyer: I don't know that this is a ubuntu only problem, I started investigating because of a report in the lau mail list [16:28] Oh! Ok, let me know what you find out. [16:28] There are also reports on the controls issues about zita-ajbrdige with similar issues [16:46] So, maybe a zita-* c compatibility issue. [16:46] This actually looks different: https://lists.linuxaudio.org/archives/linux-audio-user/2022-November/115348.html [16:48] I changed the buffer from 64 to 512 and that seemed to help. I get clean audio (full loop this machine to other machine and then back) but it seems after a while it starts to crackle [16:49] disconnecting the audio source and reconnecting seems to fix it. [16:50] It does stand to reason that network is going to need a fairly large buffer. [16:50] dsp is low (less than 2%) [16:51] I am going through three switches :P ;) [17:03] So it may be settings for the network bridge, at least with jack. Pipewire with the net bridge is a different matter I think. [17:09] Right. For now, we might not be able to support it. [17:14] I may have to add the hops param to controls. [17:18] Though, even with three switches, tracepath shows: Resume: pmtu 1500 hops 1 back 1