All my bridged vst not working with cubase 14.
All grey in my vst plugins list.
I use fm7 and powercore plugins.
All are in grey and I can’t use them
All are old 32 bit vst, bridged with jbridge.
No problems (!!!) with cubase 13…
Is there anybody there with same issue ?(Sorry for my poor English,I’m Frenchie)
Thanks for your answers.
Sergio
2 Likes
I guess your bridge VSTs are all VST2 plugins, they are disabled by default in Cubase 14. To get them back you need to open the Plugin Manager and enable VST2 in the lower left corner.
Be aware that Steinberg might remove VST2 support completely in a future release, so you should start looking for other plugins, that are VST3.
1 Like
Not a good idea…imo
1 Like
My powercore hardware to trash ?
I’m not sure what you are talking about, you need to be a bit more detailed.
If it is about the disabled VST2 then this is known for several years now, VST 3 was started in 2008, so after all these years it is clear that the old release will be removed sometime. However, there is no concrete date yet announced.
Also, as far as I know, there are bridge products available that map VST2 to VST3.
Hi, Ive just read this, what are the products for bridging VST2 to VST3 ?
There are many postings about this in the forum, try to search.
The only product I know is jbridge, but I do not use it, so you need to find out what it does on your own.
No no jbridge can bridge between 32 and 64 bit vst2, never vst3.
I have a few jbridged vst2 32bit plugs and they work fine here.
If they are greyed out and not in the blacklist maybe you have hide enabled? Click on one of the greyed out plugs and look at the bottom of the plugin manager, in the right tab there should be an option to show or hide the plugin
1 Like
I don’t use it…
VST2 to VST3, Blue Cat Audio is one of them. There are probably more.
Don’t confuse this with jBridge. IIRC the developer says he will not develop a VST2 to VST 3 converter.
1 Like
For clarity…bridging vst2 to vst3 with blue cat patchwork (or any of the other solutions afaia) doesn’t work to open old projects as the vst2 are still not seen directly by the DAW.
2 Likes
Mac OS for ARM processors?
Mac OS for Intel processor?
Windows for Intel/AMD processors?
Windows for ARM?
In this case it matters to know which Processor Family and OS you’re using.
This is the #1 reason VST2 is gradually being phased out. That format typically requires a bunch of Intel specific instructions to work. It’s possible to ‘recompile’ VST2 plugins in a way that avoids such processor instructions, but if you’re dealing with a plugin that still has enough support to see that done, then chances are they’ll just provide a proper VST3 version instead.
If you’re on Windows for Intel/AMD or an Intel Mac, Cubase 14 can still host VST2 plugins (not officially supported by Stienberg anymore, but they left it in there as an option), but you need to enable them in the Studio/VST Plug-in Manager by toggling the button ‘white’ at the bottom of the Plug-in Manager.
If you are on a newer Mac with an ARM processor, you’ll need to enable Rosetta first (I’m not sure how this is done since I have no Mac, perhaps some Mac User can chime in if this is the case), and then toggle the option as shown above. Note, at some point in the future, Apple may well stop including Rosetta and supporting it in OS releases too! So…if you’re planning on keeping up with the latest and greatest Processors and OSes for Macs…stop relying on VST2 options…start finding modern replacements for your old plugins ASAP, or in the least, ‘freeze’ a version of an OS Mac that is working for you now (perhaps on a different hard drive that you can simply swap out?), as eventually, all this old Intel instruction set stuff isn’t going to work on Macs at all anymore.
I’m not sure how it works with Windows for ARM, but I’m assuming there is some kind of Intel emulation layer for that as well. I don’t know if Windows requires ‘manual’ intervention to get such a thing working, or it just happens automatically 'when intel instructions are called for by software. Again, if this is your case, hopefully someone who knows will chime in.
Some have mentioned that direct VST2 hosting will go away in some future
version of Cubase/Nuendo. Don’t panic, but do keep a version of Cubase on your system that does support it when that day comes. It’s not a problem to keep several versions of Cubase/Nuendo on the same system in order to roll back at will. I.E. I keep an old 32 bit installation of Cubase 8.5 on my system just in case I run into any old 32bit Cubase projects I need to run. I still keep Cubase SX 3 around should I run into some old .ALL format projects from the 1990s. They all still work (albeit sometimes I need to do some creative ‘plugin management’ in some cases, as they’ll each typically attempt to use the latest versions of plugins located in the usual default locations).
If you find you really need to port older projects over to the newest version(s) of Cubase/Nuendo, it should go pretty easy. The old tracks should still be in the project, you’d just need to reconnect the end points to bridged versions of the old plugins (Or better yet, opt for modern replacements for those old plugins).
Should that process fail, you’ll have options to simply open the project in Cubase 14 or older, export the stems/tracks, get the old VST2 plugins going again via bridging in the Newer Cubase version, and import/reconnect the tracks.
You’ll also be able to ‘bridge in’ VST2 plugins on fresh projects easily enough, long after Steinberg ‘drops’ native VST2 hosting. One great free solution straight away is AUDIOGRIDDER (Yes, you can run a server on the same system that hosts your DAW). Another viable free option is Kushview Element. Various commercial options are out there as well, such as Bidule from Plogue, Patchwork by Blue Cat, and Vienna Ensemble Pro.
2 Likes
I’ll keep Cubase 8.5 and SX3 on the pc then. Thanks for all the information guys.
1 Like
If you’re on Windows for Intel/AMD and have a dongle you’ll be good to go for many years to come. Cubase 14 and earlier (maybe even 15 if Steinberg keeps an option to host VST2 support in that release)…and various options to ‘bridge’ in VST2 plugins.
Apple is the one that’s most likely to eventually pull Rosetta out of the OS, and most VST2 plugins are going to REQUIRE those Intel processor instruction calls. So if you’re on a newer Mac with the custom Apple ARM processors…plan to phase out those old 32 bit and VST2 plugins…
With Windows for ARM, I’m not sure. They’re more likely to keep some sort of Intel/AMD instruction set emulation in play for a very long time, but I suppose it’s possible it might eventually go away in Windows for ARM as well.
1 Like
Thanks for the info’.
I’m using Windows 11 on a Ryzen 7 platform
1 Like
You won’t have many if any problems continuing to use your old VST2 and 32bit jBridged stuff on that machine then. Not much to worry about 
1 Like
Thanks Brian