this post was submitted on 29 Oct 2025
81 points (98.8% liked)
Linux
59281 readers
1090 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 6 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Reaper is definitely the way to go. While it is not FOSS I feel it has the spirit of Linux. It is extremely customisable and flexible and it has all the features you expect from a good DAW.
The real issue is finding instrument and effect plugins that work on Linux. The popular ones are all windows or Mac only because they depend on DRM control software that doesn't work on Linux.
Reaper is the GOAT
Another option for using vsts is to run the Windows version of reaper in wine and load in your vsts the same way.
The windows version of reaper was built with full wine compatibility in mind so doing it this way might provide less resistance than trying to get things working with yabridge
I've always struggled installing it on wine. But I've never been good at wine and other windows translation stuff outside of letting things like steam and heroic install and manage those things for me.
Yabridge exist for windows plugins. Surprisingly works pretty good. My arturia pack works w/o any major issues. There is some virtual monitor thingy I do on sway to workaround weird performance bug. But I don't think it should surface on kde for example.
As for Reaper, DAWs and Linux: Make sure to have low latency setup for pipewire. I had to configure some stuff on arch and add pipewire latency variable with lowest values that my interface can handle to launch option for reaper. I prefer playing and practicing on Linux over the windows in terms of latency now. For how messy pipewire can be, when it's setup correctly, it's magnitudes better than windows for low latency audio not just because of latency, but because of current windows audio drivers limitations. I no longer record or edit for quiet some time, so can't say how it compares to other DAWs. Also why I'm personally using reaper: it's intuitive, fast, fair price, good terms (perpetual license with updates, there is eol for updates, but it's focused on specific version release, and for how release cycle goes it can last almost a decade, and you can still use the older versions after update eol, but better read terms yourself), and It has trial period over which I decided that it's best suited for me.
I would be interested in any resources you have on improving latency with pipework. Windows has the ASIO driver which gives direct access to the Audi interface. I didn't think pipewire was able to match it, but I'll be glad to be wrong.
I took a brief looked at yabridge a while ago, but struggled. Sounds like I should revisit it.
https://wiki.archlinux.org/title/Professional_audio https://wiki.archlinux.org/title/PipeWire I had some stuff on arch not working from the box, and interface selecting wrong type, which added latency as well. I managed to debug most of my stuff using those 2 pages and pipewire documentation. You may not need most of it on another distro. But it's a good read either way. I changed way too much and long time ago to remember everything though. If everything setup correctly, setting lowest interface supported values for pipewire latency should do the trick (point 3.1.3 on pipewire arch wiki page), without it pipewire will default to the default config option, hence why you probably felt the delay.