There should be an a audio focused distro. I think one way to solve this problem - it’s been am minute - is to host VSTs on a network node and access them over the network.
This takes a bit of doing and dedication but that is one approach.
It’s pretty exotic and not your use case…but for some it works well.
Check out VST virtual racks – audiogridder is one, there are others. I would assume any low-latency audio distr worth it’s salt would have it prewired…no idea what actual latency would be like, and how well it works.
Muse receptor was a linux based “VST in a hw rack” soln for a hot minute … it was linux (maybe suse???) + wine + tweaks. the idea there was why run vsts on your computer, run them in a receptor and process the audio like hw synth…controlling the receptor via midi??? They can be found for cheap as chips today.
This was a bigger thing back when 8 cores came from dual quad cores…not as big a deal today, when 8 core / 16 thread CPU laptops are consumer level devices.
All of this is probably not very great workflow for someone looking for an integrated solution. Some people are into the journey, and that’s cool. Others just want to make music, and that’s cool too.
Audiogridder is a recent example, remote vst kinda/sorta local. Have no idea about sample latency or how well it works from Linux pov.
There are other remote vst hosts/“virtual rack” as well as pro audio Linux distros that are focused on lower latency than windows.
It’s worth noting that … for a while?
There were rackable VST hosts running Linux & wine, the muse receptor.
The kinda fell by the wayside as large core count chips made them extra but for a moment they were a thing.
It was a cool concept, strap virtual instruments and treat it them as a hw unit. But that’s before 8 core / 16 thread consumer laptops became a thing, back when 8 cores were dual quad core chips…
so on the real
There should be an a audio focused distro. I think one way to solve this problem - it’s been am minute - is to host VSTs on a network node and access them over the network.
This takes a bit of doing and dedication but that is one approach.
It’s pretty exotic and not your use case…but for some it works well.
That’s a great interim workaround. Do you know if it’s been documented anywhere?
Check out VST virtual racks – audiogridder is one, there are others. I would assume any low-latency audio distr worth it’s salt would have it prewired…no idea what actual latency would be like, and how well it works.
Muse receptor was a linux based “VST in a hw rack” soln for a hot minute … it was linux (maybe suse???) + wine + tweaks. the idea there was why run vsts on your computer, run them in a receptor and process the audio like hw synth…controlling the receptor via midi??? They can be found for cheap as chips today.
This was a bigger thing back when 8 cores came from dual quad cores…not as big a deal today, when 8 core / 16 thread CPU laptops are consumer level devices.
All of this is probably not very great workflow for someone looking for an integrated solution. Some people are into the journey, and that’s cool. Others just want to make music, and that’s cool too.
Audiogridder is a recent example, remote vst kinda/sorta local. Have no idea about sample latency or how well it works from Linux pov.
There are other remote vst hosts/“virtual rack” as well as pro audio Linux distros that are focused on lower latency than windows.
It’s worth noting that … for a while?
There were rackable VST hosts running Linux & wine, the muse receptor.
The kinda fell by the wayside as large core count chips made them extra but for a moment they were a thing.
It was a cool concept, strap virtual instruments and treat it them as a hw unit. But that’s before 8 core / 16 thread consumer laptops became a thing, back when 8 cores were dual quad core chips…