Are you still using 32-bit plugins on PC?

[cleverr1]

Jbridge works perfectly in Cubase 10 and Cubase 10.5

Thanks! That solved it!
But, seriously, all 32-bit plugs get blacklisted for me, with no bridging occurring at all.

JBridge 1.75 is working great here in Cubase 10.5 as it did with 10. Have you tried putting the original 32 bit .dlls in a folder that Cubase doesn't look at and then creating a new folder for the bridging files which Cubase is configured to scan?

My 32 bit .dlls are in C:\Program Files (x86)\Steinberg\VstPlugins\[vendor directory] and to keep things tidy I created a directory C:\Program Files\Steinberg\JBridged where I told JBridger to put the bridging files. So long as the JBridged folder is in the list of VST2 plugin paths it works perfectly.

[zvenx]

I think part of the issue is not only the extra time 32 bit plugins require to be done (remember too Many developers have families), but also bug testing and fixing for people who are still using 32 bit plugins.

rsp

[cleverr1]

I understand the impulse to cling to VST2 as a security blanket. But keep in mind that support and maintenance for VST2 was discontinued in 2013, and the VST3 SDK no longer ships with a VST2.4 subset as of October 2018 (Steinberg gave developers a generous 5 year window to switch over to VST3). Developers who are still developing VST2 plugins are using an outdated VST SDK. Over time, this will present a problem for developers still using that last SDK with 2.4 support as VST3 continues to diverge from it. The sooner they cut the cord, the better.

That's worrying. So if VST2 gets deprecated would even be technically possible for a developer to create something to bridge a 32 bit .dll to a VST3 version?

[synaesthesia]

Jbridge works perfectly in Cubase 10 and Cubase 10.5

Thanks! That solved it!
But, seriously, all 32-bit plugs get blacklisted for me, with no bridging occurring at all.

JBridge 1.75 is working great here in Cubase 10.5 as it did with 10. Have you tried putting the original 32 bit .dlls in a folder that Cubase doesn't look at and then creating a new folder for the bridging files which Cubase is configured to scan?

My 32 bit .dlls are in C:\Program Files (x86)\Steinberg\VstPlugins\[vendor directory] and to keep things tidy I created a directory C:\Program Files\Steinberg\JBridged where I told JBridger to put the bridging files. So long as the JBridged folder is in the list of VST2 plugin paths it works perfectly.

I might have to check I have the latest version, for one thing, now I think of it. But, I'll also check the foldering (is that a word?) situation too. Thanks.

[zvenx]

I have been begging SoundRadix to developer their 32 bit alive software for Windows. It is orders of magnitude easier to use than jbridge and mbridge (or whatever the mac version is called) ( I have a license for both j and m bridge and found them a pita to use personally)

https://www.soundradix.com/products/32-lives/
rsp

[Dandy Dust]

I have just established my own vintage studio with my old pc and ableton live 8 and maudio2626 audio interface (just great). All on XP 32bit - offline and simple. 32bit very much apprichiated!