Hacker News new | past | comments | ask | show | jobs | submit login

Making electronic music is so much more than just operating system support.

You need a DAW and most of the ones that you get on Linux are horrible, except Bitwig. So you would be forced to use only one DAW.

Most of the well known plugins like Serum, LFO Tool and Massive are not available either so you would be limited to the ones included in Bitwig or the basic VSTs that you find for Linux.

And while JACK is pretty good at low latency audio you would miss out on the ASIO control panel provided by your sound card driver. While its possible to get asio working on linux using wineasio, it's a cumbersome process since you need to compile the asio dlls which have licensing restrictions.

You would have a much better experience if you just install Windows on KVM and use PCI passthrough for your sound card.






Surge isn't a replacement for Serum, but the original developer cofounded BitWig. It's probably the best sound you'll get out of a Linux-native synth. You can even use Serum wavetables with it.

> Most of the well known plugins like Serum, LFO Tool and Massive are not available either

Though everything that those VSTs can do, can also be done in Bitwig Studio starting from v3.

> miss out on the ASIO control panel

What does this add that the usual tools in Linux can't fix? Also, it's recommended to go with class compliant USB audio interfaces or otherwise interfaces that are supported on Linux. Going with MOTU gear for example is a bad idea.


"Can do" is not particularly useful. You "can" sit there and sequence thousands of sine waves in audacity to create any sound that you want... but nobody wants to do that.

Bitwig's grid is capable, but the ease of access for particular workflows is burdensome. Replicating Serum in the grid isn't possible practically, both because of filter designs and the wavetable capabilities, and getting close requires some significant acrobatics.

Massive... much easier. LFO Tool, basically impossible to replicate in Bitwig because the main draw is the _workflow_.

Bitwig is a very capable, fun and useful product for electronic music creation but I think your response to the OP is correct on a very technical, and pedantic level, but extremely unhelpful regardless.


Complaining about some missing functionality is also extremely unhelpful. Those of us who've been doing it for years know what the state of things is, and the developers of those closed source plugins know what their stance is. You ask them to do a Linux port and they say "no that would cost too much money and we can't support it". You ask them for source so you can port it yourself and they say "no you're going to steal it". You try to clean-room reverse engineer and write a clone of the plugin and they still get angry at you for "stealing". I don't bother anymore. People just have their workflow that they learned on plugins from 10 years ago, they aren't going to change unless something breaks horribly, and that's that. Those who are brave can still fiddle around with running VSTs in Wine.



Applications are open for YC Summer 2020

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: