[johntraitor]

Forget everything I said. I just spent an hour trying to fix things because you motivated me. I found out there was an issue with my Focusrite and my pipewire config. By setting the config to "Pro-Audio" in PAVU (Pulse-Audio Volume Control) in the configuration tab for my interface and disabling all others. As well as changing the the `jack.conf` with according node latency that I copied from `/usr/share/pipewire/jack.conf` to `/etc/pipewire/jack.conf`, restarting pipewire, wireplumber and disconnect/reconnect my inerface then running `pw-metadata -n settings 0 clock.force-quantum 256` (with the quantom value I set in the `jack.conf`. I have now amazing latency (5ms) even in Native Instrument. (of course I did overkill and did all i could find on internet, with more time we could pin down to the few things that really fixed the issue, sorry to send all those informations like that).

[altonas]

Do you think it'd be possible to make a shell script that anyone (running the same distro as you) could run to get all of this working? Alternatively just a readme detailing every single thing you did (and how you did it) would also make for an interesting read.

[johntraitor]

From the testing I did, the main culprit for the latency I was experiencing with my USB interface and my MIDI controller was the fact that my Pipewire profile wasn't set as `pro audio` (which can be set in PulseAudio Volume Control software in the `Configuration` tab for your USB audio interface). However as its a full profile, it must be one of the specific setting inside that fixes the issue, but I don't know which one. I might need to look into Wireplumber settings (the session manager I use for Pipewire instead of the default one `pipewire-sessions-manager`)

On another note, I found out that my focusrite was held back by factory defaults (3rd gen) and needed to follow a procedure to unlock higher samplerate. Now I am using 1024/192000 Hz and I reach 5.3ms latency without XRuns. (although when the pro audio profile isn't set Ardour would still say that the latency is 5.3 however you can clearly hear its not the case).

[johntraitor]

Good morning!(i am back from the dead). I think the best would be that I first pinpoint which parameter was the culprit (also given what I read it might be related to which sound card we use). Then we could see whether a short tutorial or a script would be the best. My first idea was to do an installation video of Archlinux fron scratch for Pro-audio, however i can understand that you would like to use your own distribution. I will try to see tonight (if i have time) what exactly was the issue and then explain how to solve it. Hopefully i could have a better understanding of what happened.