Can't get LinVST3 to work

[Linuxmusician01]

I successfully compiled and used LinVST for VST2 plugins. Works just fine in Carla-rack.

However, I can't seem to get LinVST3 to work for VST3. I compiled and installed it (I think: successfully). If I'm not mistaken then you have to rename the file linvst3.so to the name of the VST3 plugin. For example: if your VST3 is Synthi V.vst3 in the dir ~/.wine/drive_c/Program Files/Common Files/VST3/ then place linvst3.so in that same dir ad rename it to to Synthi V.so.

When I let Carla-Rack scan for new VST3 plugins then I do not see it searching in the dir I've set in Carla's settings. And the Synthi V plugin does not show up. The VST2 version of the same plugin does show up when I do the same thing (with the VST2 version of LinVST).

Wine version: wine-6.14 (Staging)


P.S. Using the utility linvst3convert doesn't help either.

[robbert-vdh]

LinVst3 is regular old LinVst + the VST3 to VST2 adapter from the VST3 SDK. So that .so file you copied is not a VST3 plugin, but a VST2 plugin that doesn't exist outside of LinVst3 (so you for instance won't be able to share projects with anyone who uses the actual VST3 plugin). At the moment yabridge is the only way to do actual VST3 bridging on Linux.

[Linuxmusician01]

LinVst3 is regular old LinVst + the VST3 to VST2 adapter from the VST3 SDK. So that .so file you copied is not a VST3 plugin, but a VST2 plugin that doesn't exist outside of LinVst3 (so you for instance won't be able to share projects with anyone who uses the actual VST3 plugin). At the moment yabridge is the only way to do actual VST3 bridging on Linux.

Unfortunately Yabridge crashes when I let Qtractor or Carla-rack look for (native) VST's with the error below. In Qtractor after the scan the whole VST dialog window that had my VST's is empty!

Code: Select all

Unhandled exception: page fault on write access to 0x0000814c in 32-bit code (0x100c508c).
Register dump:
 CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b
 EIP:100c508c ESP:0032f8a4 EBP:0032f8a8 EFLAGS:00010202(  R- --  I   - - - )
 EAX:00000000 EBX:01b70020 ECX:01b70020 EDX:00350094
 ESI:01b70020 EDI:01cc51cc
Stack dump:
0x0032f8a4:  01b70020 0032f948 100dd1ef 00000001
0x0032f8b4:  01cc51a0 0032f8f8 7bc59ce4 00000000
0x0032f8c4:  6e6f7257 6e692067 6c617473 6974616c
0x0032f8d4:  6f206e6f 6f792066 58207275 2d534c49
0x0032f8e4:  2062616c 67756c70 01006e49 0044c448
0x0032f8f4:  01cc51cc 0032f928 7bc59d8b 0000001c
Backtrace:
=>0 0x100c508c EntryPoint+0xffffffff() in xils 3.2 (0x0032f8a8)
  1 0x100dd1ef EntryPoint+0xffffffff() in xils 3.2 (0x0032f948)
  2 0x100ace0c EntryPoint+0xffffffff() in xils 3.2 (0x0032f9ac)
  3 0x100e31d1 EntryPoint+0xffffffff() in xils 3.2 (0x0032f9cc)
  4 0x10089e9b EntryPoint+0xffffffff() in xils 3.2 (0x0032f9d8)
  5 0x7e832b33 _ZN10Vst2BridgeC2ER11MainContextNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES7_i+0x452() in yabridge-host-32 (0x0032fd08)
  6 0x7e79a689 main+0x618() in yabridge-host-32 (0x0032fec8)
  7 0x7e8c6e78 __wine_spec_exe_entry+0xf7() in yabridge-host-32 (0x0032ff28)
  8 0x7b62e700 EntryPoint+0xffffffff() in kernel32 (0x0032ff48)
  9 0x7bc5af27 EntryPoint+0xffffffff() in ntdll (0x0032ff5c)
  10 0x7bc5b5e0 EntryPoint+0xffffffff() in ntdll (0x0032ffec)
0x100c508c EntryPoint+0xffffffff in xils 3.2: movl	$0x0,0x814c(%eax)
Modules:
Module	Address			Debug info	Name (63 modules)
PE	  480000-  6e5000	Deferred        msvcrt
PE	  6f0000-  b66000	Deferred        comctl32
PE	 18d0000- 1b6d000	Deferred        gdiplus
PE	10000000-10e38000	Export          xils 3.2
PE	61740000-6182e000	Deferred        advapi32
PE	62b80000-62b8c000	Deferred        api-ms-win-core-localization-l1-2-1
PE	62fc0000-631fc000	Deferred        rpcrt4
PE	63480000-6349c000	Deferred        version
PE	63bc0000-63c03000	Deferred        shcore
PE	64a40000-64b60000	Deferred        shlwapi
PE	68500000-68652000	Deferred        combase
PE	68700000-68798000	Deferred        uxtheme
PE	68e00000-68e20000	Deferred        aclui
PE	6a400000-6a889000	Deferred        ole32
PE	6ac80000-6ac8b000	Deferred        api-ms-win-core-fibers-l1-1-1
PE	6bc00000-6bca2000	Deferred        sechost
PE	6bcc0000-6beac000	Deferred        setupapi
PE	6c9c0000-6d0a2000	Deferred        gdi32
PE	6de80000-6de8c000	Deferred        api-ms-win-core-synch-l1-2-0
PE	6ed00000-6f3c4000	Deferred        user32
PE	70b40000-70e2a000	Deferred        ucrtbase
PE	71200000-7124b000	Deferred        imm32
PE	7b000000-7b306000	Deferred        kernelbase
PE	7b600000-7b923000	Dwarf           kernel32
PE	7bc00000-7bea3000	Dwarf           ntdll
ELF	7d000000-7d005000	Deferred        <wine-loader>
ELF	7d44a000-7d452000	Deferred        libxfixes.so.3
ELF	7d452000-7d45f000	Deferred        libxcursor.so.1
ELF	7d45f000-7d474000	Deferred        libxi.so.6
ELF	7d474000-7d479000	Deferred        libxcomposite.so.1
ELF	7d479000-7d488000	Deferred        libxrandr.so.2
ELF	7d488000-7d494000	Deferred        libxrender.so.1
ELF	7d494000-7d49c000	Deferred        libxxf86vm.so.1
ELF	7d49c000-7d4a1000	Deferred        libxinerama.so.1
ELF	7d4a1000-7d5f0000	Deferred        libx11.so.6
ELF	7d5f0000-7d607000	Deferred        libxext.so.6
ELF	7d62a000-7d6dd000	Deferred        winex11<elf>
  \-PE	7d650000-7d6dd000	\               winex11
ELF	7d7d3000-7d7dd000	Deferred        libuuid.so.1
ELF	7d7dd000-7d809000	Deferred        libexpat.so.1
ELF	7d809000-7d857000	Deferred        libfontconfig.so.1
ELF	7d857000-7d875000	Deferred        libz.so.1
ELF	7d875000-7d8b4000	Deferred        libpng16.so.16
ELF	7d8b4000-7d97a000	Deferred        libfreetype.so.6
ELF	7d97a000-7d9a5000	Deferred        gdi32.so
ELF	7d9a5000-7e3d6000	Deferred        shell32<elf>
  \-PE	7d9e0000-7e3d6000	\               shell32
ELF	7e4d6000-7e4f5000	Deferred        libbsd.so.0
ELF	7e4f5000-7e514000	Deferred        libgcc_s.so.1
ELF	7e6f3000-7e722000	Deferred        libxcb.so.1
ELF	7e745000-7e980000	Dwarf           yabridge-host-32<elf>
  \-PE	7e770000-7e980000	\               yabridge-host-32
ELF	7e980000-7eb07000	Dwarf           libwine.so.1
ELF	7eb2a000-7eb32000	Deferred        libxdmcp.so.6
ELF	f7abb000-f7ad2000	Deferred        user32.so
ELF	f7af2000-f7bf7000	Deferred        libm.so.6
ELF	f7bf7000-f7c02000	Deferred        librt.so.1
ELF	f7c02000-f7cdc000	Deferred        ntdll.so
ELF	f7cdc000-f7ecb000	Deferred        libc.so.6
ELF	f7ecb000-f7ed1000	Deferred        libdl.so.2
ELF	f7ed1000-f7ef4000	Deferred        libpthread.so.0
ELF	f7efa000-f7f00000	Deferred        libxau.so.6
ELF	f7f19000-f7f46000	Deferred        ld-linux.so.2
Threads:
process  tid      prio (all id:s are in hex)
00000038 services.exe
	0000003c    0
	00000040    0
	0000004c    0
	00000070    0
	0000007c    0
	000000a0    0
	000000b8    0
	000000e0    0
00000044 winedevice.exe
	00000048    0
	00000054    0
	00000058    0
	0000005c    0
00000060 winedevice.exe
	00000064    0
	00000074    0
	00000078    0
	00000080    0
	0000008c    0
	00000090    0
	00000094    0
00000068 explorer.exe
	0000006c    0
	000000cc    0
	000000d0    0
00000098 plugplay.exe
	0000009c    0
	000000a4    0
	000000a8    0
	000000ac    0
000000b0 svchost.exe
	000000b4    0
	000000bc    0
	000000c0    0
000000d8 rpcss.exe
	000000dc    0
	000000e8    0
	000000ec    0
	000000f0    0
	000000f4    0
	000000f8    0
	00000774    0
00000744 start.exe
	["C:\windows\syswow64\start.exe" /exec /home/my_name/.local/share/yabridge/yabridge-host-32.exe.so VST2 "/home/my_name/vst/XILS 3.2 FX.dll" "/run/user/1000/yabridge-XILS 3.2 FX-06BCEGqr" 19413]
	00000748    0
0000074c yabridge-host-32.exe
	["Z:\home\my_name\.local\share\yabridge\yabridge-host-32.exe.so" VST2 "/home/my_name/vst/XILS 3.2 FX.dll" "/run/user/1000/yabridge-XILS 3.2 FX-06BCEGqr" 19413]
	00000750    0
	00000754    0
	00000760    0
00000758 winedbg.exe
	[winedbg --auto 1868 136]
	0000075c    0
	0000077c    0
00000764 explorer.exe
	00000768    0
	0000076c    0
	00000770    0
00000780 start.exe
	["C:\windows\syswow64\start.exe" /exec /home/my_name/.local/share/yabridge/yabridge-host-32.exe.so VST2 "/home/my_name/vst/XILS 3.2.dll" "/run/user/1000/yabridge-XILS 3.2-4TWcdjwy" 19441]
	00000784    0
00000788 (D) Z:\home\my_name\.local\share\yabridge\yabridge-host-32.exe
	["Z:\home\my_name\.local\share\yabridge\yabridge-host-32.exe.so" VST2 "/home/my_name/vst/XILS 3.2.dll" "/run/user/1000/yabridge-XILS 3.2-4TWcdjwy" 19441]
	0000078c    0 <==
	00000790    0
	0000079c    0
System information:
    Platform: i386 (WOW64)
    Version: Windows 10

I think that's because some VST's (like Xils) want to show a message that I need a serial number to activate it etc. I did not have this problem with LinVST nor with Carla's Windows VST bridge function.

[robbert-vdh]

<snip>
I think that's because some VST's (like Xils) want to show a message that I need a serial number to activate it etc. I did not have this problem with LinVST nor with Carla's Windows VST bridge function.

The plugin (from xils 3.2.dll) segfaults during its initialization code. You're using the 32-bit version of the plugin, did you check whether the 64-bit version does work under Wine? Wine may also print some useful errors that can help you identify what's going on. I did test the demo of XILS 3 with Wine Staging (or rather, wine-tkg) 6.14 though and both the 32-bit and the 64-bit version work completely fine here in a clean Wine prefix:


So some things for you to try are:

1. Check if there are any useful errors or warnings in the log. Qtractor will print all plugin output to the log window, but you can also have it written to a file if you launch Qtractor from the command line with `env YABRIDGE_DEBUG_FILE=/tmp/yabridge.log YABRIDGE_DEBUG_LEVEL=1 qtractor`. Doing that will also add some more useful tracing information to the log.
2. Install the plugin to a clean Wine prefix, and try the 64-bit version of the plugin. Both the 32-bit and the 64-bit version of the demo work completely fine here though.
3. Since the full version of the plugin uses iLoK, make sure iLoK is running in the background when you start the plugin scan.

[Linuxmusician01]

I got it working once yesterday. It showed the VST3 version of the 'Arturia Synthi V' synthesizer (link demo version). That synth has a VST2 and a VST3 version. I use it to test VST3. It showed up with [vst3] between square brackets after the synth name. I don't know if that's the way Yabridge or LinVST3 shows the VST3's name.

For the life of me, I can't get it to work anymore!

I deleted all the Yabridge .so files from my VST2 folder because Yabridge crashes and leaves the VST list in my DAW empty if a VST wants to show a dialog window (e.g. for a serial number or if isn't properly installed).

I reconfigured Yabridge for only VST3's. I've got one VST3 and that is the 'Arturia Synthi V'. It wont show up anymore no matter if I use Yabridge or LinVST3. Deleted the ~/.vst3 folder, the .so files from LinVST and Yabridge, re-configurend Yabridge, set the VST3 path n my DAW (Qtractor) and Carla-rack. Nothing helps.

[robbert-vdh]

I got it working once yesterday. It showed the VST3 version of the 'Arturia Synthi V' synthesizer (link demo version). That synth has a VST2 and a VST3 version. I use it to test VST3. It showed up with [vst3] between square brackets after the synth name. I don't know if that's the way Yabridge or LinVST3 shows the VST3's name.

For the life of me, I can't get it to work anymore!

I deleted all the Yabridge .so files from my VST2 folder because Yabridge crashes and leaves the VST list in my DAW empty if a VST wants to show a dialog window (e.g. for a serial number or if isn't properly installed).

I reconfigured Yabridge for only VST3's. I've got one VST3 and that is the 'Arturia Synthi V'. It wont show up anymore no matter if I use Yabridge or LinVST3. Deleted the ~/.vst3 folder, the .so files from LinVST and Yabridge, re-configurend Yabridge, set the VST3 path n my DAW (Qtractor) and Carla-rack. Nothing helps.

If it showed up in the VST2 list with [VST 3] after it, then that's LinVst3. Yabridge create an actual VST3 plugin. You'll need to take a look at that log file to see what's going on. Could you please go through the three things I asked at the bottom of my last post?

[Linuxmusician01]

If it showed up in the VST2 list with [VST 3] after it, then that's LinVst3. Yabridge create an actual VST3 plugin. You'll need to take a look at that log file to see what's going on. Could you please go through the three things I asked at the bottom of my last post?

Thanks for your reply. So unintentionally I probably got LinVST3 working once!

I did what you asked:

1. Qtractor's full log when I run it with the command you recommended is here. Qtractors message window says it shorter:

   Code: Select all

   15:34:32.827 Logging started --- zo aug. 15 15:34:32 2021 ---
   15:34:32.893 Session closed.
   15:34:32.939 Session started.
   15:34:32.940 New session: "Untitled1".
   15:34:33.238 MIDI connections change.
   15:34:33.473 Audio connections change.
   qtractor_vst_scan: /usr/lib/vst/carla.vst/carla-bridge-lv2.so: plugin file error.
   qtractor_vst_scan: /usr/lib/vst/carla.vst/libcarla_interposer-jack-x11.so: plugin file error.
   qtractor_vst_scan: /usr/lib/vst/carla.vst/libcarla_interposer-safe.so: plugin file error.
   qtractor_vst_scan: /usr/lib/vst/carla.vst/libcarla_interposer-x11.so: plugin file error.
   qtractor_vst_scan: /usr/lib/vst/carla.vst/libcarla_native-plugin.so: plugin file error.
   qtractor_vst_scan: /usr/lib/vst/carla.vst/libcarla_utils.so: plugin file error.
   qtractor_vst_scan: /usr/lib/vst/carla.vst/styles/carlastyle.so: plugin file error.
   qtractor_vst_scan: /home/michel/.vst3/yabridge/Synthi V.vst3/Contents/x86_64-linux/Synthi V.so: plugin file error.
   

2. I dont know if Arturia's Synthi V is 64 bit or 32 bit. But it's installed clean and the plugin is relatively new so I think it's 64 bit (Carla-rack's vst3 bridge says: 64 bit).
3. I used another VST now then the Xils one so I don't think it's iLok-ed. Xils is VST2, I now use Arturia's 'Synthi V' VST3.

[robbert-vdh]

If it showed up in the VST2 list with [VST 3] after it, then that's LinVst3. Yabridge create an actual VST3 plugin. You'll need to take a look at that log file to see what's going on. Could you please go through the three things I asked at the bottom of my last post?

Thanks for your reply. So unintentionally I probably got LinVST3 working once!

I did what you asked:
<snip>

Thanks! The log file only loads the 32-bit 'Model_Mini' plugin, and it looks like the end was cut off. It loads Is it supposed to end there on line 106? There should be much more after that. But, I think the problem is that you were scanning for VST2 plugins! This line below:

Code: Select all

qtractor_vst_scan: /home/michel/.vst3/yabridge/Synthi V.vst3/Contents/x86_64-linux/Synthi V.so: plugin file error.

Means that Qtractor tried to load that 'Synthi V.so' as a VST2 plugin. And because it's not a VST2 plugin but a VST3 plugin, that obviously fails. So what you need to do is to tell Qtractor to look for VST3 plugins, like so:



Then it will scan for VST3 plugins. It sounds like you've added ~/.vst3 to Qtractor's VST2 plugin search location, so you should remove that because there won't be any VST2 plugin in there. And of course while you're at it you can check if Qtractor is actually searching for VST3 plugins there.

[glowrak guy]

I could never think of a reason to add any path to a wrapper's search, that wasn't inside of a .wine folder.
The .vst, .vst3, and .lv2 are for linux plugins that don't need to be wrapped anyway. And I never have
weird troubles beyond my typical typos. Thanks for your ongoing support and work on yabridge!
Cheers

[Loki Harfagr]

I could never think of a reason to add any path to a wrapper's search, that wasn't inside of a .wine folder.
The .vst, .vst3, and .lv2 are for linux plugins that don't need to be wrapped anyway.

not forcing anything here nor pretend it is a "reason", just to give one "usage", which is mine
I use a specific path to the bridge search parms in the form of a separated directory (eg: ~/.vst.YAB or ~/.vst.LV, you get the flavor) which contains links to the actual winvst paths, I started this use long ago (in dark times when yab was not even half a cell and old saurus bridges ruled the land, or crashed it) and some of my win plugins were notorious killers for some bridges and some where not or vice versa, thus it was an "easy" (very relative term in this world of wine and black&blue screens) way to "maintain" some stability.

Given the abilities of the recent bridges this old way of mine is probably out of time and overkill so I sometimes wonder if someday I'll take some time to save the busboy and start with a cleansing and use a recent standard way, the I pick up my guitar and play, just like yesterday, uh, sorry got me wandering

[Linuxmusician01]

[...]
Thanks! [...] I think the problem is that you were scanning for VST2 plugins! This line below:
[...]


Then it will scan for VST3 plugins. It sounds like you've added ~/.vst3 to Qtractor's VST2 plugin search location, so you should remove that because there won't be any VST2 plugin in there. And of course while you're at it you can check if Qtractor is actually searching for VST3 plugins there.

Thank you for posting that screenshot. Opened my eyes. I recently upgraded my distro to the latest long term release Ubuntu (20.04 'Focal'). I forgot that the Qtractor version in that distro might be a tiny bit too old to have VST3 support. And indeed, I've got Qtractor version 0.9.12 and version 0.9.13 is the first one with VST3 support.

I'm gonna look for the most easy way to install a newer version of Qtractor other than compiling from source. AFAIK the KXStudio repo's don't have Qtractor anymore.

However, the strange thing is that the Carla-rack version that I have (ver. 2.1.0) actually does support VST3 but the Yabridged VST3 doesn't show up there either. Very strange...

[robbert-vdh]

Thank you for posting that screenshot. Opened my eyes. I recently upgraded my distro to the latest long term release Ubuntu (20.04 'Focal'). I forgot that the Qtractor version in that distro might be a tiny bit too old to have VST3 support. And indeed, I've got Qtractor version 0.9.12 and version 0.9.13 is the first one with VST3 support.

I'm gonna look for the most easy way to install a newer version of Qtractor other than compiling from source. AFAIK the KXStudio repo's don't have Qtractor anymore.

However, the strange thing is that the Carla-rack version that I have (ver. 2.1.0) actually does support VST3 but the Yabridged VST3 doesn't show up there either. Very strange...

Ah, yeah, you will need a somewhat recent version of Qtractor! Didn't think of that. And the VST3 support in the earliest couple of Qtractor versions that supported it was a also bit spotty (I think it took three releases with some bug reports before it could run yabridge plugins flawlessly), so you'll really need the latest version here. Your Carla also does not yet support VST3 plugins, I think support for that was added in version 2.2.0.

[Linuxmusician01]

Thank you for posting that screenshot. Opened my eyes. I recently upgraded my distro to the latest long term release Ubuntu (20.04 'Focal'). I forgot that the Qtractor version in that distro might be a tiny bit too old to have VST3 support. And indeed, I've got Qtractor version 0.9.12 and version 0.9.13 is the first one with VST3 support.

I'm gonna look for the most easy way to install a newer version of Qtractor other than compiling from source. AFAIK the KXStudio repo's don't have Qtractor anymore.

However, the strange thing is that the Carla-rack version that I have (ver. 2.1.0) actually does support VST3 but the Yabridged VST3 doesn't show up there either. Very strange...

Ah, yeah, you will need a somewhat recent version of Qtractor! Didn't think of that. And the VST3 support in the earliest couple of Qtractor versions that supported it was a also bit spotty (I think it took three releases with some bug reports before it could run yabridge plugins flawlessly), so you'll really need the latest version here. Your Carla also does not yet support VST3 plugins, I think support for that was added in version 2.2.0.

Thanks for the tip on using the latest Qtractor version. Luckily my Carla version does support VST3 (see screenshot below). I got the 'Synthi V' vst3 version working in it. Strange thing is that I have to reboot my PC sometimes for the vst3 to work. Killing every Wine process with "wineserver -k" isn't enough...



BTW, I've started a separate topic about the easiest way to upgrade Qtractor.

[robbert-vdh]

Thanks for the tip on using the latest Qtractor version. Luckily my Carla version does support VST3 (see screenshot below). I got the 'Synthi V' vst3 version working in it. Strange thing is that I have to reboot my PC sometimes for the vst3 to work. Killing every Wine process with "wineserver -k" isn't enough...



BTW, I've started a separate topic about the easiest way to upgrade Qtractor.

That's Carla's own Wine bridge. Note how in your screenshot you're filtering by 'Bridged (Wine)' and not by 'Native', and how the right column says 'Architecture: win64'. Carla 2.1.0 does not support native Linux VST3 plugins, that was added in Carla 2.2.0. In versions of Carla that do support VST3 plugins, you can also just drag-and-drop the entire .vst3 directory from ~/.vst3/yabridge onto Carla instead of going through the whole scanning process.

[Linuxmusician01]

Thanks for the tip on using the latest Qtractor version. Luckily my Carla version does support VST3 (see screenshot below). I got the 'Synthi V' vst3 version working in it. Strange thing is that I have to reboot my PC sometimes for the vst3 to work. Killing every Wine process with "wineserver -k" isn't enough...

<snip>

BTW, I've started a separate topic about the easiest way to upgrade Qtractor.

That's Carla's own Wine bridge. Note how in your screenshot you're filtering by 'Bridged (Wine)' and not by 'Native', and how the right column says 'Architecture: win64'. Carla 2.1.0 does not support native Linux VST3 plugins, that was added in Carla 2.2.0. In versions of Carla that do support VST3 plugins, you can also just drag-and-drop the entire .vst3 directory from ~/.vst3/yabridge onto Carla instead of going through the whole scanning process.

Again, thanks for the explanation. That means I'll have to update Carla too!