Nuri wrote:Or what is the definition of "Linux plugins"?
A true “insert_os_name_here plugin” should be usable in multiple hosts. If it's limited to only one of available applications, then it can't be considered as a native to any OS, only to the host it's supported by. Well, imagine if you don't use Reaper on any OS, and somebody tells you that ReaJS plugins are Linux native now. The first thing that sparkles in your mind will be: “How can I use them in Ardour/Carla/QTractor/Bitwig Studio/whatever else?”. And then you find out that it's impossible unless you switch to Reaper. It's a simple fact: if it's not re-usable, it can't be considered of full value. Calf Plugin Pack, for instance, can be truly considered Linux native, as it can be used in a multitude of Linux hosts.
davephillips wrote:Thanks to a module from developer Rcomian some JSFX scripts can be run natively in VCV Rack.
Let's start with “some”. This already means that not all of them are usable in another host, which narrows down their usage to a very limited set of circumstances. Also, there are problems with VCV Rack's UI, at least on KDE Neon, which is about to become the base distribution for KXStudio. The problem I encountered is severe: I can not use any of embedded input/output plugins, as their interface isn't drawn completely (the only thing drawn is the text label), therefore dysfunctional. There's no way to connect to inputs and outputs if they are absent on the canvas, so the whole idea of using ReaJS on, say, my setup, is pointless, as I will never use Reaper, and VCV Rack doesn't work on it as expected. If you're curious about why I would never ever launch Reaper again, the reason is its routing system: no busses (how come? It's presented as a professional
DAW!), sends/inserts/whatever require too much hassle to even create (and I thought Cubase was a mess), VCAs are of even more fiddling around… It's not that I've got that baby duck syndrome, I easily switch to Pro Tools or Logic if somebody using it requires my help.