![]() LV2 will likely be even harder to justify unless these frameworks make it really easy for developers. Getting AU and AAX out is already something you see many small developers only do when they already have their foot out of the door. ![]() VST3 isn't perfect, but it's GPL (v3), allows building for all three platforms, including third party bridges for ProTools (Logic? tho, probably not I guess), and with cross-platform frameworks that have cross-platform UI support, like JUCE or IPlug, you're likely to have just one codebase for all three platforms - and platforms are like the biggest nightmare most developers usually deal with (see ). I haven't touched C++ in years, and never programmed plugins, but at the very least I don't think this is a huge issue. they get the "luxury" of Mac OS running on Wintel hardware (with associated low prices). not Windows software that uses WINE API layer to run, but actually written for Linux), I assume they get better performance and perhaps even better latency (using a lowlatency or RT kernel), less crashes and their OS is free (as in beer, as well as in speech). If you've ever witnessed a spinning ball of death you know that, unlike Linux, even Mac OS isn't that resilient to crashing/hanging.ĭue to all this, if one would be running all-native audio stack (i.e. The OS is also super-stable, even if some UI app were to succeed to hang the entire UI (which is a feat unto itself) a simple Ctrl + Alt+ F1 drops you into a non-graphical terminal that runs alongside your UI (usually available on the C+A+F7 "screen") and from which you can kill the offending app and go on about your day. The filesystems that are commonly used (ext4 and btrfs) are much snappier than NTFS and decently faster than even APFS (used in latest Mac OS-es) and thus add to the overall feel of the OS snapiness. Even if you are using GNOME which is really bloated, let alone something less bloated like XFCe which I use. the OS and the GUI use significantly less RAM and CPU - consequently leaving more for your applications. ![]() Linux performs significantly better than either Windows or Mac OS on equivalent hardware i.e. I say this is a long time 100% linux user but still, I have to be realistic and try not to give anyone any bad advice.ĭisclaimer: I don't really use Linux for audio (largely because my DAW of choice and the plugins I prefer to use simply work better on WIndows) but I use it as a workday driver, and I believe I can understand why someone would pick Linux as their daily OS to the point of doing audio with it. thats the reality of it and thats probably the way its going to be for a while since linux is not that user friendly, (despite what many fanboys will tell you). You really have to be prepared to troubleshoot. if your sound card is not compatible you might be out of luck. you will probably be all set with the hardware you already have since alsa has a lot of drivers these days in it for all kinds of sound cards. To resume: get kxstudio or some other linux music distribution to save you loads of time. Since I dont have any midi hardware the latency is not that big of a deal for what I do at the moment. ![]() Kxstudio is really the way to go if you want it to be as hasslefree as possible.Īt the moment since I had to separate from hardware I use FL studio on linux with wine which works perfectly except that I havent been able to get wineasio to work + jack + fl studio together which would make it low latency so, not really low latency but it doesnt crash in the middle of a session so thats good at least. ![]() Its a hassle UNLESS, you have compatible sound hardware and you run something like kxstudio which brings all the things necessary by default like jack server, ardour, ladspa, lv2 etc. My experience so far (started with linux in 2007, make some music with it from 2012 onwards (still using it)) ![]()
0 Comments
Leave a Reply. |