Ok,
Final word is... sticking with JACK/Pulse/pajackconnect. PipeWire is just fine as a general Desktop Audio system, this isn't some tribal issue... Looking at it from a Distribution viewpoint it requires too much tweaking for Pro Audio work and is not really of enough benefit to throw out a system that has proven itself for many years now, it's as simple as that.. Now that I have that off the plate I can get to the business of updating stuff and hopefully mint some test ISO's soon.
AV Linux 23 PipeWire tests and tools.
Re: AV Linux 23 PipeWire tests and tools.
Looking forward to it !
Re: AV Linux 23 PipeWire tests and tools.
Question for you: With this new OS coming up what would be to best way to go about having Youtube running at the same time than Reaper ?
I managed to have it running before with Qjackctl patching under alsa but ended up with a bunch of xruns and crackling. I'm not too savy with jack just barely gets me going.
I managed to have it running before with Qjackctl patching under alsa but ended up with a bunch of xruns and crackling. I'm not too savy with jack just barely gets me going.
Re: AV Linux 23 PipeWire tests and tools.
Hi, on a default AV Linux setup:
Generally... Fire up Qjackctl and select the Audio device you want to use and that is connected to your speakers/headphones. Regardless of all the performance tweaks in AV Linux every system has a hugely variable threshold for Xruns so if you are going to juggle JACK and the PulseAudio bridging etc. maybe don't drop the frames per period too low right off the bat, keep it a 512 or 1024 at first just to see how everything works, you can always reduce it later. Once Qjackctl is running it will start JACK, the PulseAudio JACK bridging components and also a2jmidid so your MIDI devices are available for both JACK and ALSA..
Now fire up Reaper and in it's Audio Setup utility select the 'JACK' backend, this way Reaper is connected to JACK and by proxy to the Audio device you selected in Qjackctl... If you want to watch a YouTube Video now no problem... Fire up Firefox (or whatever Browser you use) and the Browser will be connected to PulseAudio and routed to JACK via the PulseAudio JACK modules that were automatically started with Qjackctl..
In effect Reaper is connected to your Audio device via JACK and YouTube is connected to your Audio Device via PulseAudio's JACK modules and everything is funneled to the Audio Device and speakers..
Generally... Fire up Qjackctl and select the Audio device you want to use and that is connected to your speakers/headphones. Regardless of all the performance tweaks in AV Linux every system has a hugely variable threshold for Xruns so if you are going to juggle JACK and the PulseAudio bridging etc. maybe don't drop the frames per period too low right off the bat, keep it a 512 or 1024 at first just to see how everything works, you can always reduce it later. Once Qjackctl is running it will start JACK, the PulseAudio JACK bridging components and also a2jmidid so your MIDI devices are available for both JACK and ALSA..
Now fire up Reaper and in it's Audio Setup utility select the 'JACK' backend, this way Reaper is connected to JACK and by proxy to the Audio device you selected in Qjackctl... If you want to watch a YouTube Video now no problem... Fire up Firefox (or whatever Browser you use) and the Browser will be connected to PulseAudio and routed to JACK via the PulseAudio JACK modules that were automatically started with Qjackctl..
In effect Reaper is connected to your Audio device via JACK and YouTube is connected to your Audio Device via PulseAudio's JACK modules and everything is funneled to the Audio Device and speakers..
Re: AV Linux 23 PipeWire tests and tools.
Thank you will try this soon, and see how it works this time.