12-12-2018, 02:58 PM | #1 |
Human being with feelings
Join Date: Nov 2011
Posts: 971
|
Feature Request: Native Windows/Wine VST(i) Bridge
Are we now on par with the Windows version of Reaper? I would LOVE to see an integrated, seamless Windows-native VST bridge that works with WINE. Something where I simply point to the paths in WINE where I've installed the Windows VST(i)s, and Reaper does the rest. :-)
I think for the for the next several years, it will be something that is very beneficial for Linux users (especially refugees from the MS Windows camp; as well as for everyone involved, since it will make things much more efficient for everyone as well. :-) Is this something we can even hope for in the near future? I'd honestly place this as a higher priority than even native Lv2 support. Last edited by audiojunkie; 12-13-2018 at 01:04 PM. |
12-12-2018, 08:24 PM | #2 |
Human being with feelings
Join Date: Jan 2012
Location: North East UK
Posts: 493
|
What's wrong with linvst?
__________________
http://librewave.com - Freedom respecting instruments and effects http://xtant-audio.com/ - Purveyor of fine sample libraries (and Kontakt scripting tutorials) |
12-13-2018, 02:50 AM | #3 | |
Human being with feelings
Join Date: May 2014
Location: France
Posts: 259
|
Carla (with windows vst bridge) works fine.
But it needs more cpu than native vst. Quote:
If you want to use lot of (or mostly) windows vst, run reaper in Windows, it's safer et more stable. |
|
12-13-2018, 09:55 AM | #4 |
Human being with feelings
Join Date: Jul 2016
Location: Los Angeles, CA
Posts: 1,701
|
A Windows to Linux VST Bridge is going to be critical for any widespread adoption of Reaper on the Linux platform. While LinVst is really great and has made things possible that a couple years ago simply weren't, it places a lot of onus on the end user and a lot of testing and fiddling to try and see what works, what will work, what won't, etc. Having a windows to native Linux bridge in Reaper itself would help a great deal towards this and make it a lot less daunting to users trying to jump into the Linux pool, myself included.
|
12-13-2018, 10:29 AM | #5 |
Human being with feelings
Join Date: Nov 2018
Posts: 63
|
+1 for sub26nico
as I am understanding the situation a "native" winvst bridge would still depend on wine (and the constand changes and updates in wine) and so every cross platform use would still be fragile? I think it s more important to show plugin developers that it ´s not hard to port to linux and that there is money in the game for them when they follow the example of U-he, overtone, airwindows and all the others who already port to linuxvst. Keep writing to plugin developers and asking if you can use their product on linux and sometimes I remember this already had an effect.... |
12-13-2018, 12:34 PM | #6 | |
Human being with feelings
Join Date: Nov 2011
Posts: 971
|
Quote:
|
|
12-13-2018, 12:44 PM | #7 | |
Human being with feelings
Join Date: Nov 2011
Posts: 971
|
Quote:
We all know that Cockos (and ourselves) are vested in the idea of using Linux. It would make more sense to have a supported, internal, easy-to-use bridge from a company that is creating the DAW, to entice more users to the Linux world. This will also have the effect of developers like Aciddose seeing a growing population of Linux users. And as far as LV2, I suspect that if a format were to become an over all winner, it would be native VST. The number of potential VST developers could exponentially outnumber the number of LV2 developers. Windows developers wouldn't have to re-learn or re-write everything to support Linux when using Native VST. |
|
12-13-2018, 01:00 PM | #8 |
Human being with feelings
Join Date: Nov 2011
Posts: 971
|
The standard musician (think of all the Mac users out there) just wants to make music, not learn how to compile code to access his/her plugins. The new Linux enthusiast (such as myself), is willing to dig much further than the standard musician. And as I went (without help) and tried to understand everything in the instructions, I realized that the documentation, while thorough, is not quite complete, and is quite messy. I wasn't successful in getting it to work.
Now, before anyone shouts "But Hey! You can always ask us! The developer is awesome and is available right here to help! You just didn't put any effort into it", remember this: realistically, how many musicians that are not tech savvy are you likely to get to use LinVST? It's a great tool. It really is! But it is lacking. Imagine clear documentation and a supported, up-to-date FlatPak LinVST binary! Problem solved! Now, I want to be well understood. I am NOT IN ANY WAY bashing the awesome developer of this package! I'm just simply stating what you asked: What is wrong with LinVST. :-) |
12-13-2018, 03:20 PM | #9 |
Human being with feelings
Join Date: Jan 2012
Location: North East UK
Posts: 493
|
There's no compilation required. Just put the LinVST file in the same folder as the VST plugin and make sure it has the same name as the plugin. That's all.
__________________
http://librewave.com - Freedom respecting instruments and effects http://xtant-audio.com/ - Purveyor of fine sample libraries (and Kontakt scripting tutorials) |
12-13-2018, 03:49 PM | #10 | |
Human being with feelings
Join Date: Aug 2011
Location: Near a big lake
Posts: 3,943
|
Quote:
Anyway if Justin wants to go down the rabbit hole of supporting another OS' plugins on Linux, I'm not going to say "no". I just wouldn't suspect he'd be eager to do so. I'm fine with native Linux plugins. If anything I'd like to see LV2 natively in Reaper. |
|
12-13-2018, 04:54 PM | #11 |
Human being with feelings
Join Date: Apr 2018
Location: Karlsruhe
Posts: 486
|
It's also my opinion that LV2 support and more Linux plugin development is much more important than native bridging of Windows plugins. Personally I don't even have WINE installed.
__________________
https://soundcloud.com/lilith_93 https://open.spotify.com/intl-de/art...SMSwCW9VkqAN9Q MX Linux, Behringer UMC 204 HD, Neumann KH120 |
12-13-2018, 05:15 PM | #12 | |
Human being with feelings
Join Date: Nov 2011
Posts: 971
|
Quote:
I don't know much about compiling, but I know that files ending with .h or .CPP are header files and CPP code that when compiled, create the binary. I see several files with the prefix makefile. I don't see the binary. Is there a different webpage where it is located? What are the binaries. It's been a few months since I last tried or read anything from the site, but I couldn't see it before, and got the impression that it had to be compiled. A binary and clearer documentation would be very helpful! In fact, if the binary is available for download and the documentation is clear enough, LinVST will be sufficient for me. Any help would be appreciated! :-) |
|
12-13-2018, 05:21 PM | #13 |
Human being with feelings
Join Date: Nov 2011
Posts: 971
|
Oh Wow! When you told me that compiling wasn't necessary (something that I previously believed otherwise), I went back and looked and found the following:
https://github.com/osxmidi/LinVst/releases This is it, isn't it...... Wow! I feel so dumb! :-( |
12-13-2018, 06:47 PM | #14 |
Human being with feelings
Join Date: Jan 2012
Location: North East UK
Posts: 493
|
Yeah, always look for the releases tab on github and hope the dev made some binaries
__________________
http://librewave.com - Freedom respecting instruments and effects http://xtant-audio.com/ - Purveyor of fine sample libraries (and Kontakt scripting tutorials) |
12-17-2018, 12:16 PM | #15 | |
Human being with feelings
Join Date: Mar 2008
Location: Planet Earth
Posts: 9,055
|
Quote:
|
|
12-19-2018, 03:19 PM | #16 | |
Human being with feelings
Join Date: Mar 2017
Posts: 859
|
Quote:
A few temps who are marginally dumb (checking the mirror as I type) slip through the cracks, but soon become brilliant, and fully assimilate for the win. Cheers ...well, I'm still working on that 'soon' part... |
|
12-20-2018, 01:36 PM | #17 |
Human being with feelings
Join Date: Nov 2011
Posts: 971
|
Thanks for the kind words! :-)
|
Thread Tools | |
Display Modes | |
|
|