Linux is … incredible for programming … but, I need to create, not just consume!
You think that programming isn’t creative? :P
Linux is so bad
How? Serious question, what are your pain points?
FL Studio is proprietary
Stop using proprietary software that you can’t fix (or get someone to fix). :P
Try using a virtual machine if you really need to run windows, but…
The ideal solution would be to work out how to replace it in your workflow, even if that means you need to learn to code and build your own tool.
I wish I could fix that? But I can’t do it alone :)
If there’s a community that’s already out there working on similar open source software I’m sure that they would welcome new contributors with open arms; they can’t do it alone either.
Maybe you don’t know the language or can’t code, but you can still help out with documentation, triaging bugs, etc. Learning to submit useful bug reports and reproduce bugs from other users can help developers spend their time fixing bugs not working out what’s going on.
bruh - it’s better to admit Linux Open Source is janky for audio production and that its commercial offerings (bitwig, reaper, renoize et al), while awesome, are incomplete because the plugin world isn’t there.
There are some things where a Mac or Windows is just a better choice, and 100% a DAW is that place.
PLEASE NOTE: Linux is 100% the right OS for homebrew devices c/o RasberryPi. There are audio focused distros that do have some nice features but they are a different kind of journey.
Telling someone “go code” is totally unrealistic. The OP’s goal is to make music.
I’m not suggesting that someone switch over to them immediately, but accepting the status quo is a great way to ensure that it will never change. There’s no inherent reason that this software can’t run on Linux; as you’ve pointed out it’s that nobody has cared enough to do the porting.
Be the change you want to see in the world.
If you want better audio production on Linux put in some work. I provided a ton of non-coding ways that someone can contribute to those products.
I’m pragmatic enough that I suggested the use of a Windows VM.
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.
You think that programming isn’t creative? :P
How? Serious question, what are your pain points?
Stop using proprietary software that you can’t fix (or get someone to fix). :P
Try using a virtual machine if you really need to run windows, but…
The ideal solution would be to work out how to replace it in your workflow, even if that means you need to learn to code and build your own tool.
If there’s a community that’s already out there working on similar open source software I’m sure that they would welcome new contributors with open arms; they can’t do it alone either.
Maybe you don’t know the language or can’t code, but you can still help out with documentation, triaging bugs, etc. Learning to submit useful bug reports and reproduce bugs from other users can help developers spend their time fixing bugs not working out what’s going on.
bruh - it’s better to admit Linux Open Source is janky for audio production and that its commercial offerings (bitwig, reaper, renoize et al), while awesome, are incomplete because the plugin world isn’t there.
There are some things where a Mac or Windows is just a better choice, and 100% a DAW is that place.
PLEASE NOTE: Linux is 100% the right OS for homebrew devices c/o RasberryPi. There are audio focused distros that do have some nice features but they are a different kind of journey.
Telling someone “go code” is totally unrealistic. The OP’s goal is to make music.
I’m not suggesting that someone switch over to them immediately, but accepting the status quo is a great way to ensure that it will never change. There’s no inherent reason that this software can’t run on Linux; as you’ve pointed out it’s that nobody has cared enough to do the porting.
Be the change you want to see in the world.
If you want better audio production on Linux put in some work. I provided a ton of non-coding ways that someone can contribute to those products.
I’m pragmatic enough that I suggested the use of a Windows VM.
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.