Add new comment

A small update to mention I can reproduce the scenario with the Monster Drums plugin from the same developer. This would have me think these plugins share some trait exposing them to this scenario.

OK, so can I reproduce it with Carla? In order to find out, I loaded the same 2 plugins into Carla 2.5.8. Carla sees each of these VST3s as "native" since yabridge is workingi its magic. Both plugins loaded fine, were usable, and I was able to save the Carla session to /tmp/carla-test.carxp and use that file to reload both plugins after restarting Carla.

I did see something of interest in Carla's log though....

======= Starting engine =======
======= Engine started ========
Carla engine started, details:
  Driver name:  JACK
  Sample rate:  44100
  Process mode: Multi client
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] Initializing yabridge version 5.1.0
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] library:       '/home/windowsrefund/.local/share/yabridge/libyabridge-vst3.so'
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] host:          '/home/windowsrefund/.local/share/yabridge/yabridge-host.exe'
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] plugin:        '/home/windowsrefund/.vst3/win/MONSTER Drum v3-2022.07.vst3'
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] plugin type:   'VST3'
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] realtime:      'yes'
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] sockets:       '/run/user/1000/yabridge-MONSTER Drum v3-2022.07-0LWhkmvw'
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] wine prefix:   '<default>'
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] wine version:  '9.13 (Staging)'
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] 
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] config from:   '<defaults>'
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] hosting mode:  'individually, 64-bit'
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] other options: '<none>'
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] 
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] Enabled features:
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] - bitbridge support
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] - CLAP support
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] - VST3 support
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] 
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] [Wine STDERR] 002c:fixme:winediag:loader_init wine-staging 9.13 is a testing version containing experimental patches.
23:08:16 [MONSTER Drum v3-2022.07-0LWhkmvw] [Wine STDERR] 002c:fixme:winediag:loader_init Please mention your exact version when filing bug reports on winehq.org.
23:08:18 [MONSTER Drum v3-2022.07-0LWhkmvw] [Wine STDERR] Initializing yabridge host version 5.1.0
23:08:18 [MONSTER Drum v3-2022.07-0LWhkmvw] [Wine STDERR] Preparing to load VST3 plugin at '/home/windowsrefund/.vst3/win/MONSTER Drum v3-2022.07.vst3'
23:08:18 [MONSTER Drum v3-2022.07-0LWhkmvw] [Wine STDERR] Finished initializing '/home/windowsrefund/.vst3/win/MONSTER Drum v3-2022.07.vst3'
JUCE Assertion failure in juce_VST3PluginFormat.cpp:3636

Honestly, I don't grok why Carla is reporting the file as being loaded from ~/.vst/win given the fact it is reported as "Native" so I'll chalk that down as some type of symlinkish thing I'm not going to worry about. So maybe Carla is handling JUCE raising some sort of exception where Qtractor isn't? I don't know.

Again, given what I think I know about these MONSTER plugins, I'd be willing to bet they're not entirely compliant with these vst standards? As such, I'm certainly not expecting much but I'm hoping to be pleasantly surprised if the underlying issue is something simple.

All the best