Are either of those accessible from the GUI in a fresh default install? I know exactly where in Windows to find that control panel (granted they make it more convoluted to get to in every successive version), but I don’t know how I would do it with just what the OS provides in either Mint or Kubuntu (the two distros I have the most familiarity with).
I have only been rocking Linux as a daily driver for a year or two now though, so it could just be a gap in my knowledge.
No but now we get closer to the real problem. Meaning there is an accessibility problem, which is different than the (in my opinion wrong) statement that I wanted to correct.
Are you able to enable the Air function or doing any routing on your focusrite? I’ve found a way to handle sample rates on Topping Pro 2x2, and on my old focusrite 2i2. But input delays through the audio layers in linux are slower than windows and mac.
I should clarify my original comment. I’m looking for full feature parity out of the box and not having to devise some sort of work around or relay on a 3rd party and hope they don’t stop maintaining it.
It is a real frustration, I use my linux install as must as I can but somethings are limited by the lack of 1st party support.
The problem with audio interfaces is that they function very different internally and have different kind of settings. Alsamixer does usually a decent job of listing all parameters but it is an old TUI tool and not nicely embedded into the desktop so I guess people just don’t find it. Stuff like latencies just have to do with buffer sizes that are configured in your machines audio system, usually pipewire, pulseaudio or jack, which all work on top of alsa (which is where the drivers run). You can reduce the buffers there (in config files) to get lower latencies. This however means that your system needs to have a very tight scheduling for your audio processes, because if it fails to fill the buffer in time there will be glitches. Professional low latency audio does definetly not work out of the box on linux. It got a little better with pipewire, but I don’t think it works well without a little bit of tinkering. If you decide to tinker I recommend you read this:
https://wiki.archlinux.org/title/Professional_audio
I don’t remember which tool I use for my Scarlett (I’m travelling). But I googled a bit and this looks good:
This all would be better if manufacturers would provide Linux config tools like they do on windows or at least information of their protocols. Until they do we have to be greatful for people reverse engineering that stuff (e.g. by analysing USB traffic on windows) and then writing uis for it.
Edit: this site seems to make more sense as the arch wiki page (it is linked there):
Are either of those accessible from the GUI in a fresh default install? I know exactly where in Windows to find that control panel (granted they make it more convoluted to get to in every successive version), but I don’t know how I would do it with just what the OS provides in either Mint or Kubuntu (the two distros I have the most familiarity with).
I have only been rocking Linux as a daily driver for a year or two now though, so it could just be a gap in my knowledge.
No but now we get closer to the real problem. Meaning there is an accessibility problem, which is different than the (in my opinion wrong) statement that I wanted to correct.
Ah, fair enough.
Are you able to enable the Air function or doing any routing on your focusrite? I’ve found a way to handle sample rates on Topping Pro 2x2, and on my old focusrite 2i2. But input delays through the audio layers in linux are slower than windows and mac.
I should clarify my original comment. I’m looking for full feature parity out of the box and not having to devise some sort of work around or relay on a 3rd party and hope they don’t stop maintaining it.
It is a real frustration, I use my linux install as must as I can but somethings are limited by the lack of 1st party support.
The problem with audio interfaces is that they function very different internally and have different kind of settings. Alsamixer does usually a decent job of listing all parameters but it is an old TUI tool and not nicely embedded into the desktop so I guess people just don’t find it. Stuff like latencies just have to do with buffer sizes that are configured in your machines audio system, usually pipewire, pulseaudio or jack, which all work on top of alsa (which is where the drivers run). You can reduce the buffers there (in config files) to get lower latencies. This however means that your system needs to have a very tight scheduling for your audio processes, because if it fails to fill the buffer in time there will be glitches. Professional low latency audio does definetly not work out of the box on linux. It got a little better with pipewire, but I don’t think it works well without a little bit of tinkering. If you decide to tinker I recommend you read this: https://wiki.archlinux.org/title/Professional_audio
I don’t remember which tool I use for my Scarlett (I’m travelling). But I googled a bit and this looks good:
https://blog.rtrace.io/posts/fedora-support-focusrite-scarlett/
This all would be better if manufacturers would provide Linux config tools like they do on windows or at least information of their protocols. Until they do we have to be greatful for people reverse engineering that stuff (e.g. by analysing USB traffic on windows) and then writing uis for it. Edit: this site seems to make more sense as the arch wiki page (it is linked there):
https://this.ven.uber.space/docs/computer/pro-audio/