Automigration of VST plugins does no longer work in Cubase Pro 14.0.10

[Felix_Schmenger]

Cubase Pro 14.0.10, Windows 10

Steps to reproduce:

1. Create an empty project
2. Add an old version of your VST-plugin that supports automigration (tested with Kontakt 7)
3. Save the project and close cubase
4. Remove all but the newest version (tested with Kontakt8.vst3) of the respective plugin from the VST plugin folders (paths can be determined from looking at Studio->VST Plugins Manager)
5. Restart cubase
6. Check under Studio->VST Plugins Manager that only the newest version of the plugin (Kontakt 8) shows up
7. Reload the project

Cubase complains that the plugin is missing. The instance is not migrated

Expected behavior:
Cubase should auto-migrate the VST instance stored within the project (Kontakt 7) to it`s newer available version (Kontakt 8). The steps above work in Cubase 13.0.51.

[Jorge_Ruiz]

@Felix_Schmenger

Remove all but the newest version (tested with Kontakt8.dll) of the respective plugin dll from the VST plugin folders (paths can be determined from looking at Studio->VST Plugins Manager)

Wasn’t this automigration of plugins a VST3-only feature? Because that “Kontakt8.dll” you mention looks to be a VST2 plugin.

[Felix_Schmenger]

Hi Jorge,
no, starting from Kontakt 6 they are VST3`s. They obviously have the file suffix .vst3, not .dll as I stated above.

[KT66]

Post deleted.

[Felix_Schmenger]

Yeah my bad, I edited my original problem description now to avoid confusion.

[Googly_Shakespeare]

@Felix_Schmenger

automigration

I’ve never heard of this. I was under the impression that VSTech uses plugin IDs. If a dev changes the ID, then Cubase will complain.

[Felix_Schmenger]

You can read more about it
here: Cubase automatically replaces some plug-ins used in old projects? - #6 by steve
and here: https://support.native-instruments.com/hc/en-us/articles/12972701353757-Notes-about-Auto-Migration-of-Kontakt-Versions-in-DAW-Projects
Since this used to work well in an older Cubase version with exactly the same plugins, I assume the problem is not on NI`s side.

[KT66]

Here’s another thread on the subject. I know Ted had already upgraded to Cubase 14 by then. He’s on a Mac though.

Kontakt 8

For those of you who upgraded from Kontakt 7 to Kontakt 8, here’s a trick to avoid having to set up all your routing and buses, etc. all over again when loading a song that had Kontakt 7. Simply remove the Kontakt7 vst from your VST3 folder, and rename the Kontakt8 vst in there to Kontakt7. When your song with Kontakt 7 loads, you will get a message saying “Kontakt 7 is not present, it has been replaced with Kontakt 8”. Everything will load and your setup will still be intact. I have successfull…

[lokotus1]

sample problem here with Cubase 14.0.20. (win)
nuendo 13 does it well (same project tested) and newest Cubase updates fail to do proper plugin migration … please fix

[tenkas]

I tried on Cubase 14.0.41, MacOs Sequoia
Kontakt 6 (full) migrate to Kontakt 7 player or Kontakt 8 player.

I can’t get it to work.

[tenkas]

FOUND SOLUTION:
I was using Kontakt 7 player or Kontakt 8 player.

I purchased Kontakt 8 (full) and migration works! Doing some more test but it seems to work! Great!

According to Evil Dragon (on VI forum), the binaries are the same for kontakt player and kontakt full.

He says this is a Cubase issue.

If possible, please flag this for DEV team.