KVR Audio

Domlun · Post by **Domlun** » Sat Feb 15, 2025 8:31 pm

I just upgraded to cubase 14 for the batch freeze ability and now I fear it was $250 wasted

Existing projects have ALL VST2 instruments unloaded.

When I go to plug in manager and turn on VST2, it rescans and finds them in the plug-in manager, but it doesn't then load them on the tracks.

Even if I save the project in Cubase 14, WITH THE VST2 OPTION TURNED ON IN PLUG-IN MANAGER, when I open the project again, VST2 is turned off again. Why?

If I had known I couldn't open existing projects in Cubase 14 fully/correctly, of course I never would have upgraded.

concealed identity · Post by **concealed identity** » Sun Feb 16, 2025 2:15 am

Please keep us updated if you figure out a solution to this! I'm planning on upgrading to Cubase 14 at some point, but this would be a big problem for me.

mountainmaster · Post by **mountainmaster** » Sun Feb 16, 2025 4:28 pm

Sorry, no help from me either but thanks for the warning. I guess I will stick with Cubase 13 for now.

zvenx · Post by **zvenx** » Sun Feb 16, 2025 5:23 pm

SB announced the upcoming end of vst 2 three years ago.
https://helpcenter.steinberg.de/hc/en-u ... scontinued
It would have made sense to start using vst 3 in your projects from then.
That said I am surprised once you enable vst2 it doesnt open existing projects as saved.
Are you on mac or windows?

rsp

zvenx · Post by **zvenx** » Sun Feb 16, 2025 5:25 pm

Also:

Can I open any previous Cubase version with my Cubase 14 license?

With your Cubase 14 license you can open Cubase 12 and Cubase 13, but no Cubase generation before that as these were activated using the eLicenser license management system. Of course you can use Cubase 14 to open projects created in previous versions.

https://www.steinberg.net/cubase/faq/#: ... 20versions.

Maybe download cubase 12 and 13 and use those.
Mountainmaster seems to suggest cubase 13 is fine so download and use that.

rsp

Resonant- Serpent · Post by **Resonant- Serpent** » Sun Feb 16, 2025 6:50 pm

Post on the Cubase forum. Much more likely to get an answer over there.

I've had zero issues running VST2 plugs in Cubase. You might need to disable the VST3 versions of the VST3 plugins you're trying to use.

Weasel-Boy · Post by **Weasel-Boy** » Fri Feb 21, 2025 6:42 pm

I think it’s on the plug-in management menu. C14 defaults with VST2 plug-ins unloaded. You can uncheck that and your VST2s will load under Rosetta.

RobGee · Post by **RobGee** » Fri Feb 21, 2025 9:39 pm

Never encountered that issue myself (Windows 11 Pro) but the only VST 2 plugins I still use are the Lexicon PCM Bundle and mostly that is loaded in Bluecat Patchwork.

As others have said try Cubase 13 as your license is valid for that version.

Weasel-Boy · Post by **Weasel-Boy** » Sat Feb 22, 2025 2:02 am

Weasel-Boy wrote: Fri Feb 21, 2025 6:42 pm I think it’s on the plug-in management menu. C14 defaults with VST2 plug-ins unloaded. You can uncheck that and your VST2s will load under Rosetta.

This.png

mountainmaster · Post by **mountainmaster** » Sun Feb 23, 2025 12:09 am

Weasel-Boy wrote: Sat Feb 22, 2025 2:02 am
Weasel-Boy wrote: Fri Feb 21, 2025 6:42 pm I think it’s on the plug-in management menu. C14 defaults with VST2 plug-ins unloaded. You can uncheck that and your VST2s will load under Rosetta.
This.png

Didn't the OP already do that?

Domlun wrote: Sat Feb 15, 2025 8:31 pmWhen I go to plug in manager and turn on VST2, it rescans and finds them in the plug-in manager, but it doesn't then load them on the tracks.

concealed identity · Post by **concealed identity** » Sun Feb 23, 2025 9:53 pm

Yeah it sounds like the issue is that old projects always open with VST2s disabled, so they don't load when the projects are open, but enabling them doesn't load the ones you'd previously used into the track. It seems that, for some reason, VST2s are disabled again after reopening the file.

Weasel-Boy · Post by **Weasel-Boy** » Sun Feb 23, 2025 10:42 pm

mountainmaster wrote: Sun Feb 23, 2025 12:09 am
Didn't the OP already do that?

Who knows? The OP hasn't been back in over a week.

On an M1 Macbook running C14 under Rosetta, Cubase 14 has no issue running/loading 64 bit VST2 plugins used on a ton of older Projects created all the way back to at least Cubase 9.5. At least they do over here. But when I first launched C14, I had to hit that switch to get everything to work. So I guess YMMV.

paramita123 · Post by **paramita123** » Mon Feb 24, 2025 12:46 am

Works for me with older projects on C14 Pro, just got to switch on the button as demonstrated, then wait patiently for them to be scanned.
One word of caution, some users have experienced instability ~ I would personally advise to restrain from wildly installing all sorts of stuff and keep the DAW OS clean. I will do a dual boot soon and have a dedicated music OS with the bare minimum and will test potential new plugins in the old OS before deciding to copy over or not.
C14 is generally really good and I love the Modulators.

AdvancedFollower · Post by **AdvancedFollower** » Mon Feb 24, 2025 10:23 am

No issues opening old projects here. When enabling VST2, make sure they're all being scanned and make sure all folders where you've installed VST2's are included in the path.

mountainmaster · Post by **mountainmaster** » Sat Apr 05, 2025 12:39 pm

Reporting back here to alleviate any concerns others may have with the v14 upgrade.
I took the plunge and upgraded to Cubase 14. So far no issues at all for projects with VST2 plugins.

Just to be sure I enabled VST2 the first time I started Cubase 14 before opening any projects and let it finish the scan. Since then I have quit and started Cubase 14 several times and VST2 stays enabled.

So it seems the OP's issue was an isolated case. Since the OP also reported another issue related to settings I think the problem may be a corrupted preferences file.

Cubase 14 Wont Open Existing Projects Correctly