And a lot of these devsĪre small-budget shoestring efforts, if not freeware. Improving wine and vst wrappers is more important. Where is _need_ for native linux ports? It can be argued that This widely done, old style VST developers will be able to follow and provide native Linux versions.īut if the 'old-style' vsts's work that well (and many do, I've been using them for years) They will just install their beloved VSTs on the Linux box and be happy and safe. With decently "bridged" Windows VST support, people would not even notice that there is some Windows based technology behind the screens handled by WineLib. Mostly this is due to Wine not fully implementing the support needed by a plug-in, bugs, or possibly the need for a special configuration of wine. Some will work perfectly, others partially, and some won't work at all. Note that this still is not a perfect solution and results will vary depending on what plug-ins you are trying to use. I'll try to list them here, if any are missing, please let me know and I'll add them to the list:Īll of the above solutions use Wine to provide the OS support needed by the plug-ins, though they differ in how they are implemented and how they can be used in REAPER. REAPER so far has no builtin bridge to run Windows VST(I)s on Linux, but there are several third party utilities that can help. I've created this thread to discuss running Windows VST(I)s in REAPER on Linux.Īny discussions on various solutions, programs, development, bugs, feature requests, tips and tricks, etc are on topic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |