32 bit VST plugins are not recognised on a 64 bit Windows build of Ardour 6.2

I’d like to use the excellent dblue Glitch plugin in Ardour. I’m using the old version that was released gratis by the developer, and is 32 bit. My Ardour build is 64 bit. I’m running Windows.

It seems that a 64 bit version of Ardour will not load 32 bit VSTs. Are there any known workarounds for this?

Relevant logs - note that for plugins where I have both versions installed, only the 64 bit version is recognised.

2020-07-25T12:56:50 [INFO]: --- Windows VST plugins Scan: C:\Program Files\Common Files\VST3;C:\Program Files (x86)\Steinberg\VSTPlugins;C:\Users\ftwie\lmms\vst;C:\Program Files\Steinberg\VSTPlugins
2020-07-25T12:56:50 [INFO]:  *  C:\Program Files (x86)\Steinberg\VSTPlugins\Dexed.dll - i386 (32-bit)
2020-07-25T12:56:50 [INFO]:  -> Cannot get Windows VST information, plugin ignored.
2020-07-25T12:56:51 [INFO]:  *  C:\Users\ftwie\lmms\vst\dblue_Crusher.dll - i386 (32-bit)
2020-07-25T12:56:51 [INFO]:  -> Cannot get Windows VST information, plugin ignored.
2020-07-25T12:56:51 [INFO]:  *  C:\Users\ftwie\lmms\vst\dblue_Glitch_v1_3.dll - i386 (32-bit)
2020-07-25T12:56:51 [INFO]:  -> Cannot get Windows VST information, plugin ignored.
2020-07-25T12:56:51 [INFO]:  *  C:\Users\ftwie\lmms\vst\dblue_Stretch.dll - i386 (32-bit)
2020-07-25T12:56:51 [INFO]:  -> Cannot get Windows VST information, plugin ignored.
2020-07-25T12:56:52 [INFO]:  *  C:\Users\ftwie\lmms\vst\dblue_TapeStop.dll - i386 (32-bit)
2020-07-25T12:56:52 [INFO]:  -> Cannot get Windows VST information, plugin ignored.
2020-07-25T12:56:52 [INFO]:  *  C:\Users\ftwie\lmms\vst\Obxd.dll - x64 (64-bit)
2020-07-25T12:56:52 [INFO]:  -> OK (VST Plugin "Obxd" was added).
2020-07-25T12:56:53 [INFO]:  *  C:\Users\ftwie\lmms\vst\Synth1\Synth1 VST.dll - i386 (32-bit)
2020-07-25T12:56:53 [INFO]:  -> Cannot get Windows VST information, plugin ignored.
2020-07-25T12:56:53 [INFO]:  *  C:\Users\ftwie\lmms\vst\Synth1\Synth1 VST64.dll - x64 (64-bit)
2020-07-25T12:56:54 [INFO]:  -> OK (VST Plugin "Synth1 VSTi" was added).
2020-07-25T12:56:55 [INFO]:  *  C:\Users\ftwie\lmms\vst\Tunefish4.dll - x64 (64-bit)
2020-07-25T12:56:55 [INFO]:  -> OK (VST Plugin "Tunefish4" was added).
2020-07-25T12:56:55 [INFO]:  *  C:\Program Files\Steinberg\VSTPlugins\Andes-1.dll - x64 (64-bit)
2020-07-25T12:56:56 [INFO]:  -> OK (VST Plugin "Andes-1" was added).
2020-07-25T12:56:56 [INFO]:  *  C:\Program Files\Steinberg\VSTPlugins\Dexed.dll - x64 (64-bit)
2020-07-25T12:56:56 [INFO]:  -> OK (VST Plugin "Dexed" was added).
2020-07-25T12:56:57 [INFO]:  *  C:\Program Files\Steinberg\VSTPlugins\helm.dll - i386 (32-bit)
2020-07-25T12:56:57 [INFO]:  -> Cannot get Windows VST information, plugin ignored.
2020-07-25T12:56:57 [INFO]:  *  C:\Program Files\Steinberg\VSTPlugins\helm64.dll - x64 (64-bit)
2020-07-25T12:56:57 [INFO]:  -> OK (VST Plugin "Helm" was added).
2020-07-25T12:56:57 [INFO]:  *  C:\Program Files\Steinberg\VSTPlugins\Voxengo\SPAN.dll - x64 (64-bit)
2020-07-25T12:56:58 [INFO]:  -> OK (VST Plugin "SPAN" was added).
2020-07-25T12:56:58 [INFO]: --- Windows VST plugins Scan Done
2 Likes

Thanks. Thinking about it it makes sense since Ardour runs VSTs in-process so they have to match the architecture…

Use a bridge, like jBridge for example - https://jstuff.wordpress.com/jbridge/

It would be great to have an “integrated bridge” like modern DAWs (such as ACID Pro has).

An integrated bridge is neither old or modern but rather design choice. Ardour has a number of users that use well over 100 tracks. Sand boxing plugins does not scale well for that use. Using a bridge for one or two plugins makes a lot more sense and helps the user to be more aware of what plugins they choose to use and how they affect system performance.

1 Like