robbert-vdh / yabridge

A modern and transparent way to use Windows VST2, VST3 and CLAP plugins on Linux
GNU General Public License v3.0
2.25k stars 55 forks source link

All Puremagnetik vsts not working #310

Open martblek opened 5 months ago

martblek commented 5 months ago

Thanks for giving yabridge a shot!

Problem description

Plugins do not appear in any DAW after 'yabridge sync'

What did you expect to happen?

working plugins ?

What actually happened?

VST2 plugins is not processed using yabridgectl and VST3 plugins not working in any DAW. I think that error causes CabbageAudio export to VST but who knows because if i export source from Cabbage to VST plugin it works.

Operating system

Manjaro

How did you install yabridge?

AUR

yabridge version

5.1.0-2-g49e696e4

yabridgectl version

5.1.0

Wine version

Wine-8.2.1 (Stagging) (tested in others versions, still same issue)

Plugin

All from Puremagnetik

Plugin type

both VST2 and VST3

Plugin architecture

64-bit

Host

Renoise 3.4.3, Reaper 7.11, Bitwig 5.1.3

Desktop environment or WM

Xfce4

GPU model

Nvidia RTX 3060 Ti

GPU drivers and kernel

No response

Debug log

yabridge.log

Anything else?

[2024-02-17 12:48:22.743 float-library-metadata info] Starting plugin host process with command: /opt/bitwig-studio/bin/BitwigPluginHost-X64-SSE41 metadata 1234 6 2 PluginHost: Connecting to metadata service with id 6 on port 1234 using id 2 PluginHost: Metadata connection established [2024-2-17 12:48:22.749 info] PluginHost: Reading VST 3 plugin metadata for /home/martin/.vst3/yabridge/Expanse.vst3 terminate called without an active exception [2024-02-17 12:48:23.269 float-library-metadata info] Closing connection with plugin host: There was an error communicating with the plugin host: java.io.EOFException [2024-02-17 12:48:23.274 indexer info] Could not read metadata for yabridge/Expanse.vst3 com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: com.bitwig.flt.library.metadata.reader.exception.CouldNotReadMetadataException: could not read metadata: Communications error with plugin host process exit code:134 stdout: [2024-2-17 12:48:22.749 info] PluginHost: Reading VST 3 plugin metadata for /home/martin/.vst3/yabridge/Expanse.vst3

stderr: terminate called without an active exception

martblek commented 5 months ago

Sorry VST2 have same issue as VST3. Wrong path added. sorry for mistake

robbert-vdh commented 5 months ago
12:48:25 [Foomph-49BHabhs] [Wine STDOUT] Aplikace nemohla b�t spu�t�na nebo nen� ��dn� aplikace asociov�na s dan�m souborem.
12:48:25 [Foomph-49BHabhs] [Wine STDOUT] ShellExecuteEx selhal: Cesta nenalezena.

Sounds like the drive assignments in your Wine prefix are messed with. Open winecfg, go to the drives tab, and make sure the default entry for the Z: drive pointing to your file system root is there (or something similar so Wine can find yabridge's files).

martblek commented 5 months ago

Ah, yes i have Z: pointing to my home directory :( but others plugins works as expected. Pointing Z: to "/" solved this issue but another appears. There is only small black window. I playing with yabridge.toml but without luck. here is yabridge.log ya.log