osxmidi / LinVst

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

My DAW can't load my pugins #200

Closed p1xlized closed 3 years ago

p1xlized commented 3 years ago

Hi i changed recently my os, and i did like always(moved files from linvst folder to /usr/bin). It didn't work. When my DAW(bitwig) started indexing the plugins an error pop up with following: "Error linvst.dll not found"

That's the error as shown in DAW: /run/media/alex/2f99cec4-9224-418e-bda4-aad1b5f4c03e/Plugins/VST/Serum_x64.so

com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Communications error with plugin host process
exit code:139
stdout:
PluginHost: Reading VST 2.4 plugin metadata for /run/media/alex/2f99cec4-9224-418e-bda4-aad1b5f4c03e/Plugins/VST/Serum_x64.so

does someone has an idea.

i have tried lin-vst-X and still nothing.

UPD. wine version is 6.15 , that was my error sorry for that.

osxmidi commented 3 years ago

Hi i changed recently my os, and i did like always(moved files from linvst folder to /usr/bin). It didn't work. When my DAW(bitwig) started indexing the plugins an error pop up with following: "Error linvst.dll not found"

* wine 6.5

* Daw Bitwig-studio 4.0.1

That's the error as shown in DAW: /run/media/alex/2f99cec4-9224-418e-bda4-aad1b5f4c03e/Plugins/VST/Serum_x64.so

com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Communications error with plugin host process
exit code:139
stdout:
PluginHost: Reading VST 2.4 plugin metadata for /run/media/alex/2f99cec4-9224-418e-bda4-aad1b5f4c03e/Plugins/VST/Serum_x64.so

does someone has an idea.

i have tried lin-vst-X and still nothing.

That happens when there is a (unnamed) linvst.so file somewhere in your vst folder paths.

Also

For Bitwig 2.5 and 3.x, In Settings->Plug-ins choose "Individually" plugin setting and check all of the LinVst plugins. For Bitwig 2.4.3, In Settings->Plug-ins choose Independent plug-in host process for "Each plug-in" setting and check all of the LinVst plugins.

p1xlized commented 3 years ago

The name of linvst.so match the windows .dll files. Usually i store them on my other drive and when i reinstall my os just install the libraries and host for them. This time it didn't work for some reason. i tried many things, still doesn't work Screenshot from 2021-08-30 10-10-10

osxmidi commented 3 years ago

The name of linvst.so match the windows .dll files. Usually i store them on my other drive and when i reinstall my os just install the libraries and host for them. This time it didn't work for some reason. i tried many things, still doesn't work Screenshot from 2021-08-30 10-10-10

Bitwig can be strange imo.

I've had an actual linvst.so file (linvst binary unzipped in the Download folder) in the Downloads folder and Bitwig tried to load it causing a linvst.dll error like your one.

The Downloads folder was not in the vst path that I set in Bitwig.

The only thing I can think of is that Bitwig was scanning my Downloads folder of it's own accord.

So I moved the unzipped linvst folder (that was in the Downloads folder) to my home folder and Bitwig didn't scan the linvst.so file.

If a Daw scans the actual linvst.so file (from say a linvst binary unzipped folder) then it will produce a linvst.dll not found error because there is no linvst.dll, linvst.so hasn't been renamed to match a genuine vst dll file name.

The same thing will happen if there is an actual linvst.so file in any of the Daw's vst paths.

So that might be throwing Bitwig into a bit of a spin.

I'd try moving the folder that contains the actual linvst.so file to your home folder.

Also there might be problems with the Serum Bitwig scan, so maybe install linvst again (to /usr/bin) and then redo the name conversion in your vst paths (linvstconvert).

p1xlized commented 3 years ago

Downgraded to 6.14 works perfectly. Thanks for your help.