search

osxmidi / LinVst

Linux Windows vst wrapper/bridge
GNU General Public License v3.0
682 stars 41 forks source link

Waves plugs V13 not working #210

Closed guglielmofratticioli closed 2 years ago

guglielmofratticioli commented 2 years ago

I have linvst 4.5 with wine v17, Reaper fails to scan Waveshell1-VST 13.0, so all the v13 waves plugins fail. On the other hand v11 and v12 works fine

osxmidi commented 2 years ago

Keeping up with Waves changes is always difficult.

I'll try to see what is happening but no guarantees.

guglielmofratticioli commented 2 years ago

Have you checked out the solution by yabridge vst bridge? The waves v13 are working fine with that , well actually I don’t know how much is it different from linvst and if you can find a fixing strategy in there

osxmidi commented 2 years ago

Have you checked out the solution by yabridge vst bridge? The waves v13 are working fine with that , well actually I don’t know how much is it different from linvst and if you can find a fixing strategy in there

Well, they do their thing and I do mine, whatever.

The trouble with Waves is that they changed to using Powershell and Powershell is very flaky with Wine.

Wine needs to incorporate Powershell in an official way.

Who knows what Waves will change for Windows 11 and whether Wine can handle it.

iLok is another one, but iLok (software licenses) is pretty good with Wine at the moment.

It could be an installation problem or maybe some hack is needed.

Unofficial installation problems could be anything.

I've done hacks for Waves, but it gets to a point of whether it's worth it just for them, given Wine's limitations.

I might get around to looking into it.

osxmidi commented 2 years ago

I've just had a look at it.

I tried it out on EndeavourOS (arch based) and wine-staging 6.22 and Reaper and LinVst 4.5.2.

I installed Waves central v13 (following my own notes in the Waves Readme) and installed a couple of demos (Bass Rider, MetaFlanger) and it seems to be ok as far as I can tell.

The installation of V13 seems the same routine as v12 to me.

Wine Staging is needed.

guglielmofratticioli commented 2 years ago

Wa Im trying that later, guess wine staging 6.22 has fixed that