I'm using JACK. But my choice is due to lack of experience rather than a conscious choice.
Most of the materials about linux setup for audio production that I relied on (moving the production machine from Windows to Linux) described JACK as a stable and robust sound server (unlike PipeWire). Those might be outdated statements.
From writings here you could get impression you did wrong thing, but actually you did what is best. Pipewire before version 1.0 does not have irq based scheduling, and therefore getting decent performance with it is matter of luck. Powerful hardware and low load helps, but does not guarantee it. And PW 1.0 is so recent (half year ago or something) that most distros don't have it. Sure there is plenty of bleeding edge hunters that come shouting 'I have been using PW from version 0.01 and no problems'. Many of them aren't recording any audio, and few xruns don't hurt, but when recording guitar, single xrun can ruin your recording.
So you have perfect system, and for it instructions are pretty clear:
- Setup you jack to use focusrite as interface, I personally use qjackctl
- run 'arecord -l' to see audio interfaces plugged, my example :
Code:
tavasti@hermo3:~$ arecord -l**** List of CAPTURE Hardware Devices ****card 1: Ultra [Fast Track Ultra], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0card 2: io2 [io|2], device 0: USB Audio [USB Audio] Subdevices: 0/1 Subdevice #0: subdevice #0 - run alsa_in with suitable parameters, in my case 'alsa_in -d hw:io2 -j second_interface' where that -d hw:io2 is critical part, selecting right hw.
Statistics: Posted by tavasti — Tue May 21, 2024 7:36 pm