I do think programming is creative, I just didn’t talk precisely about it because it wasn’t the focus of the conversation :).
Linux is very bad for music creation, the ecosystem is lacking the incredible tools like Ableton or FL studio, and the VSTs. You can’t shit done on Linux in this area right now, well I’ve made some music but what a pain it was.
I won’t stop using proprietary software just for the sake of using Linux. I need and I like FL Studio, it’s a very good DAW. Stop trying to convert everyone to your open-source utopia, it can’t exist! I love open-source, I’m an open-source contributor on a few projects and most of my projects (the good ones) are open-source too! But, try to make music with open-source tools and we can talk about it.
Some of them are good but not as good as an Omnisphere, a Serum, or a Purity, or a Ozone RX 9 for mixing.
And no, I won’t involve myself into an open-source DAW because I’ve literally got other shit to do right now than filling issues or PRs that no one will read on GitHub.
The way you talk about things is not helpful, it is just the same copy-pasted shit every time. Open-source… bugs… developers… community… proprietary software bad…
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…
Linux is very bad for music creation, the ecosystem is lacking the incredible tools like Ableton or FL studio, and the VSTs. You can’t shit done on Linux in this area right now, well I’ve made some music but what a pain it was.
So what you’re saying is that it’s possible but that the tools aren’t great right now?
I love open-source, I’m an open-source contributor on a few projects and most of my projects (the good ones) are open-source too!
It sounds like you’re in a position to make some headway on that.
try to make music with open-source tools and we can talk about it.
Some of them are good
So they’re not all ‘very bad’ then?
I won’t involve myself into an open-source DAW because I’ve literally got other shit to do right now than filling issues or PRs that no one will read on GitHub.
Why do you assume that issues or PRs won’t be read and actioned? That’s not my experience working with open source?
Stop trying to convert everyone to your open-source utopia, it can’t exist
Bullshit (and beside the point).
The way you talk about things is not helpful, it is just the same copy-pasted shit every time. Open-source… bugs… developers… community… proprietary software bad…
Stop acting like a malfunctioning cyborg.
Make me.
Edit: I did ask for actual pain points and you didn’t respond to that.
Edit2: a quick update from IRC neutroniak: lmms supports VSTs
I do think programming is creative, I just didn’t talk precisely about it because it wasn’t the focus of the conversation :).
Linux is very bad for music creation, the ecosystem is lacking the incredible tools like Ableton or FL studio, and the VSTs. You can’t shit done on Linux in this area right now, well I’ve made some music but what a pain it was.
I won’t stop using proprietary software just for the sake of using Linux. I need and I like FL Studio, it’s a very good DAW. Stop trying to convert everyone to your open-source utopia, it can’t exist! I love open-source, I’m an open-source contributor on a few projects and most of my projects (the good ones) are open-source too! But, try to make music with open-source tools and we can talk about it.
Some of them are good but not as good as an Omnisphere, a Serum, or a Purity, or a Ozone RX 9 for mixing.
And no, I won’t involve myself into an open-source DAW because I’ve literally got other shit to do right now than filling issues or PRs that no one will read on GitHub.
The way you talk about things is not helpful, it is just the same copy-pasted shit every time. Open-source… bugs… developers… community… proprietary software bad…
Stop acting like a malfunctioning cyborg.
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…
So what you’re saying is that it’s possible but that the tools aren’t great right now?
It sounds like you’re in a position to make some headway on that.
So they’re not all ‘very bad’ then?
Why do you assume that issues or PRs won’t be read and actioned? That’s not my experience working with open source?
Bullshit (and beside the point).
Make me.
Edit: I did ask for actual pain points and you didn’t respond to that.
Edit2: a quick update from IRC
neutroniak: lmms supports VSTs