#VESTIGE LMMS WINDOWS#
However, if you depend upon a project working reliably, and repeatably its probably not so good to use plugins designed for a completely different OS.Īs for including it by default there is empirical evidence that the Windows VST compatible builds of ardour (on linux) are (or certainly were) less reliable generally, so I would caution against including something by default which compromises the stability of the application (obviously I’m willing to be corrected if this is not the case, and its something the ardour devs are better able to comment on).
So, its fine if you want to experiment with windows plugins on linux (but seriously, if you’re going to run windows software, its far better to do that on windows) And when it does fail, neither you nor the developers (and you can be sure the plugin developers won’t care) will be able to do anything about it. What this means at a user level is that you can’t be at all sure that what works today might not fail inexplicably the following day (or after a WINE upgrade) - or due to the phase of the moon, or the prevailing wind direction. It makes the list of plugins you can use dependent on WINE shoot way up - and while I think WINE is an incredible achievement, its still a compatibility layer, which has had to be (reverse) engineered from a closed OS, which means that there are always going to be compatibility issues as the developers cannot know all the (undocumented) issues inherent in the OS (and the plugins), and compatibility issues between them. (and I’ll repeat it again because its based on personal experience) it effectively makes the list of plugins you can use shoot way, way up. We will NOT ever make Ardour use technology that runs Windows VST plugins in another As a commercial developer of linux plugins, whenever I mention my genuine personal opinion on this, I get accused of everything from having a commercial interest in spreading FUD about using Windows plugins on linux, to just hating WINE for some irrational reason, however, my genuine (irrespective of commercial interests) opinion is this: If you want to load Windows VST plugins into Ardour on Linux, you use a specially built version (which is actually a windows program executed with Wine). This includes what LMMS does and also what dssi-vsthost does.
#VESTIGE LMMS CODE#
I subsequently decided that although the code for this within Ardour would be loosely maintained, I would NOT support it.Īfter we did that, some other people took various approaches that used varying amounts of Kjetil’s approach and ours.
This approach scales, but turned out to be very very dependent on the precise version of Wine. This didn’t scale (for the reasons I’ve outlined above) in cases like Ardour, so I and Torben Hohn reimplemented Kjetil’s idea so that the plugins could run inside the DAW. He did so using a server-based approach, where a single server loaded all the plugins and the real “host” called the server to get stuff done.
Kjetil Mattheusen was the first person to get Windows VST’s running on Linux. Browser plugins are not executed thousands of times per second in a realtime context, and you don’t have a situation where there might be N different plugins on every track.Īnd let me clarify the history here.
0 kommentar(er)
