Hi, Here I share the new Ardour 8 ardour-pipewire-alsa.desktop to run it with ALSA-PIPEWIRE support, this shortcut is very useful for some soudcards that have the crackling audio issue with PIPEWIRE-JACK, this configuration shortcut is useful to run Ardour in very lowlatency modes without audio distortion and use ALSA with the flexibility of PIPEWIRE.
Just paste this script into a simple text editor like gedit, Kwrite etc. and save it as ardour-pipewire-alsa.desktop in /home/youruser/.local/share/applications folder so it can be accessible in the applications menu, load it and in the Audio/Midi setup select ALSA, select the soundcard to use and the buffer configuration.
I recommend qpwgraph for connections cause is more user friendly.
*this script is for Ardour 8, if you want to use it with 7.5 or 6X versions you need to modify the Exec= parameter if you know how to.
Thanks Robin for your advice, in My case, I never had good luck with any version of Pipewire-Jack, always have Xruns and Sound Crackling in buffer configurations below 512, but with this configuration I can make large projects without issue, also midi is working a breeze with no latency problems.
I recognize Pipewire is in an early stage, but also recognize that it’s the future of linux audio system, However I respect and appreciate your opinion.
yeah, that’s right, also the results can vary with different distros, in my test it work better with Arch and Fedora than X-Buntu-Debian in my lenovo v15 hardware and usb audio, however i think wont look back to Jack, I like so much plain ALSA in Ardour, but it take all the audio source of my sound card, and I can’t use OBS at the same time.
Hi Robin!, testing Pipewire for a year I need to say YOU ARE CORRECT, Pipewire is still not ready for prime time or pro-audio usage, the latency in Pipewire is more than Jack, also the xruns is considerable more than Jack, no mater the kernel, distro or hardware also some bugs, I think I’ll stay on Jack for now until the big pro like You and Paul approve it for pro-audio stuff, thanks for all your advises!
Did you select “Pro Audio” for your sound card in pavucontrol under the Config tab?
From FAQ · Wiki · PipeWire / pipewire · GitLab
“Since 0.3.81 this profile will use IRQ based scheduling with linked devices when there is 1 capture and 1 playback device. This results in the same latency as can be achieved with JACK on the device”
It wasn’t really advice. You can’t actually do what I was describing on Linux, and the closest you can get to it is via Pipewire. That’s why I said it is ironic that PW is using IRQ-based timing to get low latency.
Ok, I was so exited with Pipewire by the multi-backend feature, but testing it in different distros it’s kinda temperamental when using it for audio production even using the pipewire-alsa / pipewire-jack, I think I’ll stay on Jack until Ubuntu 24.04 be available that will be full Pipewire compiled exclusively for Ubuntu 24.04, to se how it work, but for now I can say there’s still no substitute for Jack with it stability and low xruns functionality in Linux, but say Pipewire is a great audio back-end for multimedia usage, but for pro-audio still need some love.
A common issue is that you use a too low buffersize and the system shuts down after many consecutive dropouts.
Then again, Ardour is only expected to work correctly with direct hardware access. If you use pipewire’s emulation, Audio/MIDI alignment will be incorrect, and likely overdubs when recording audio may also not align. if you [have to] use pipewire, use pipewire-jack.