Zum Inhalt der Seite gehen


So here's the thing: I'd really love to use #Ardour for my next album, cause I don't want to continue working with something from a company sucking up to America's regime

Only problem is: I can't

I'm using 3 different audio interfaces via #pipewire 1.2.4, and Ardour keeps on forgetting USB audio and MIDI connections over restarts (or suspends), forcing me to make each connection again, which sucks.

First person to solve this for me gets a present and a special credit in the liner notes.
(1/2)
Dieser Beitrag wurde bearbeitet. (5 Tage her)
p.s: I don't want to go through 12 different READMEs or compile a new pipewire or a new kernel or whatever. I simply want this to work.

Come on, it can't be that hard, can it?!

#linuxaudio

(2/2)
Dieser Beitrag wurde bearbeitet. (5 Tage her)
Qjackctl also has a persistant patchbay functionality
What version of Ardour?
so, the problem as given is a little underspecified.

Ardour certainly remembers and retains connections. Can you be more specific about the setup you have and the scenarios that fail?
many thanks for getting back to me. I have since narrowed down the problem to pipewire.

Sometimes (or more precisely: quite often) after resuming from sleep or unplugging and plugging the USB cable, pipewire "forgets" one of my audio interfaces (a Zoom AMS-44).

When that happens, Ardour can't restore connections.

The workaround seems to be restarting pipewire manually after resuming from sleep or plugging in the USB cable.

systemctl --user restart pipewire.service

🤷
this far from surprising to me. Audio-after-suspend is still a weakpoint for Linux in general.

In general, we work on Ardour assuming audio interfaces are stable from the system POV; while we have code that notices devices coming and going (with the ALSA backend), our assumption is that you don't do this while using a pro-audio application.

If you don't need inter-application routing or device sharing while using Ardour, you might have better luck with the ALSA backend.
at the moment I'm kind of relying on pipewire because I have multiple audio interfaces connected.

(or is the ALSA backend able to use more than one interface…?)
it can but it is non-trivial (there's no GUI to do it, it require environment variables).

Anyway, we strongly advise against using multiple audio interfaces (even as we acknowledge that people do this anyway).

Unless they are word-clock synced, that is.
I have to admit I'm still using Jack and Qjackctl with Ardour. Maybe the pipewire Jack emulation would be a good transition - I should try it myself.
I mainly (try to) use pipewire because that way I can use all the audio interfaces I happened to amass over the years…
I heard this can be consequence of different buffer size in Ardour session and Pipewire settings. Also, I make a post how to restore connections quick, I hope it will be useful. https://noc.social/@crimaniak/114078142498826353