ubuntustudio is pretty good about this but as mentioned, 23.10 is shipping with pipewire 0.3.79. In order to upgrade... sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream
sudo apt update
sudo apt -y install pipewire
FYI, Pipewire defaults to a sample rate of 48000 so if, like me, you want 44100, you'll need to run the ubuntustudio-config-audio tool.
I did that and also set min quantum (what I used to call buffer in the pure jack days?) to 1024 but I've just learned Pipewire goes ahead and changes this dynamically. Imagine my surprise when I'd see Qtractor and Carla reporting 256 and other values at random times.... Basically, everything can be done in ~/.config/pipewire/pipewire.conf if/when you get tired of the ubuntustudio-audio-config wrapper. I'm thinking I may want to add an override to set default.clock.quantum = 1024 in order to prevent this dynamic behavior but haven't really made up my mind on that just yet.
ubuntustudio is pretty good about this but as mentioned, 23.10 is shipping with pipewire 0.3.79. In order to upgrade...
sudo add-apt-repository ppa:pipewire-debian/pipewire-upstream
sudo apt update
sudo apt -y install pipewire
FYI, Pipewire defaults to a sample rate of 48000 so if, like me, you want 44100, you'll need to run the ubuntustudio-config-audio tool.
I did that and also set min quantum (what I used to call buffer in the pure jack days?) to 1024 but I've just learned Pipewire goes ahead and changes this dynamically. Imagine my surprise when I'd see Qtractor and Carla reporting 256 and other values at random times.... Basically, everything can be done in ~/.config/pipewire/pipewire.conf if/when you get tired of the ubuntustudio-audio-config wrapper. I'm thinking I may want to add an override to set default.clock.quantum = 1024 in order to prevent this dynamic behavior but haven't really made up my mind on that just yet.