I’m running Ardour 9.2 at 96kHz, the same as my A&H CQ18T is set to.
If I record something, Ardour only records half of it:
When changing the buffer size in the audio setup, I get a warning that the session changed to 48kHz.
The session now runs at 48kHz
When clicking “OK” in that warning, Ardour starts an endless loop displaying that same message; every time I click “OK” it returns until I manually kill the Ardour process.
I’m using PipeWire 1.6.4 on CachyOS / Arch Linux.
Have you tried Ardour/ALSA instead if JACK/Pipewire?
(Pipewire has a system wide default sample-rate, usually 48kHz, and resamples behind the scenes)
Setting the PipeWire sample rate to 96kHz fixed it!
The endless loop displaying that message was annoying though; and maybe Ardour can query PipeWire to see if it is running at the same sample rate as Ardour?
My issue is fixed now; thanks!
Ardour interacts with Pipewire via the JACK API, which does not include any facilities for changing the sample rate (only for setting it if the JACK server is not yet running). If you load a session that was created at X kHZ but Pipewire is running at Y kHz, Ardour cannot change that. The loop does seem odd - I regularly start Ardour with sessions that use a different SR than Pipewire is currently using, and have never seen this message loop occur.
