I just ran Ardour 9.5 for the first time on my system with a pre-existing jack.conf on a pipewire-jack set-up. All this worked a handful of months ago without problems. Now, on my very powerful system with a Behinger UMC404HD (which worked flawlessly for my purposes) produces Xruns galore only on Jack. Does not do the same with ALSA. Both set with latency to 128 - ALSA is clean; jack produces Xruns. This is a first. Jack used to be my gold-star standard for stability.
Something in one of my configs? Nothing’ changed in my configs, though. And when I stop the server, set the latency to 128, and start it through Ardour, I still get the same results.
Thanks for the response. I’m well aware of how to configure jack, which is why I was banging my head against the wall. Turns out, it was the webcam that was creating the issue. As soon as I unplugged it, the problem went away. I don’t quite understand why it is, and it is worth investigating in case I want to do client work while in a web conference, so I’m going to investigate.
I’m wondering if wireplumber needs to be configured for this sort of setup.
Nonetheless, that’s a separate post. I’d consider this solved, for now.
The solution, it seems, was to simply disable the audio hardware related to the webcam. Now, I can have the webcam functionality, while being able to record on Ardour using pipewire-jack. I hope this helps others who may be facing similar issues.