Sorry for the confusing title - hoping someone can help.
I’ve had this a few times over the years when upgrading a VST from say v1 to v2.
As an example I have a Cubase Pro 9 Project with 10 midi tracks. Each of these are mapped to an instance of a VST, v1. Everything is fine and normal.
However when a new major version of the same VST is released, I close Cubase and install this completely new brand new VST v2 on my system.
At this point when I next open the Project all of the tracks are still mapped to the v1 of the VST. As you would expect because the v2 is a separate VST instrument.
But is there a way that I can map them all to the new version of the VST without having to switch every track individually to the new instance of the VST manually and load each sound and VST settings individually etc?
The example I have right now is that I’ve just paid a load of money to purchase Miroslav Philharmonik 2. But I have loads of tracks using Philharmonik 1. The problem is that 1 is 32Bit and no longer works with Cubase Pro 9, hence why I upgraded.
But basically the problem is that when I load any of my previously created Projects in Cubase Pro 9 which have tracks assigned to Philharmonik 1, I get a pop-up on load saying cannot load Philharmonik 1 and then all of these midi tracks load unconnected.
If I then go through each instance that was previously connected to Philharmonik 1 and connect them to Philharmonik 2, the VST connects to these tracks but the instruments (patches) are not loaded - I’m just connecting the tracks to a fresh instance of the VST.
Ideally I would like these projects to open and know that any Philharmonik 1 track can be connected to Philharmonik 2 and the respective instruments loaded in for each track.
Can anyone please suggest anything to help?
It would be nice if I’ve missed something obvious.
Thanks a lot.