VST3 auto migration Kontakt 6 to Kontakt 7

[samphony]

Dear Devs please consider this:

Since VST3 SDK 3.7.5 (IPluginCompatibility interface) it should be possible to auto migrate Kontakt 6 to Kontakt 7.

If Kontakt 6 gets disabled or removed from the vst3 plugin folder and Kontakt 7 is present your VEP project or meta frame will load with Kontakt 7 instead.

The benefit?
No one has to manually replace Kontakt 6 with Kontakt 7.
Because manually would mean:

- one has to save each multi in each Kontakt 6 instance manually
- replace each Kontakt 6 instance with Kontakt 7
- reload all multis in each Kontakt 7 instance

auto migration would do all that automatically without the need to save multis at all!!!

[samphony]

Here is an example how its works for me in Nuendo 12

Nuendo auto migration k6 to k7

[noiseboyuk]

This request is 18 months old, but with Kontakt 8 around the corner it is more relevant than ever.

VSL folks, could you respond if this is something on your roadmap? It would be of HUGE benefit if users could have their versions of Kontakt (or any other plugin) use the latest version automatically. This is now supported by Cubase, Nuendo and Logic

https://steinbergmedia.github.io/vst3_doc/base/classSteinberg_1_1IPluginCompatibility.html

[The Minstrel]

+1 for the request.

[cgernaey]

+1 for this request. Please consider strongly doing this VSL. I have so many instances going back as far as Kontakt 5.

Thank you!!

[DareonSky]

+1 for the request too. Very important, please do it soon VSL.

[mducharme]

+1 from me too

[Shad0wLandsUK]

+1 Here as well

[noiseboyuk]

Hey VSL, Kontakt 8 is released today. Your users need to know if this is on your roadmap or not before they redo 1,000 Kontakt multis.

[bcslaam]

+1 This is a much needed feature.

Give us a sign please VSL?

[dbtothavsl]

+1 Kontakt 8 now makes this even more important

[Lindurion]

Another +1 to implement this feature please! It seems clear that NI is sticking with the approach of each new major Kontakt version as a separate plug-in, so I think there will be increasing demand for this among composers.

And ideally don't do the plug-in upgrade automatically--but some kind of choice dialog on project open (or even an on-demand menu option) when there is a newer compatible plug-in version installed would be a huge time saver for large template migration.

[noiseboyuk]

VSL, the silence is deafening.

[Davka]

+1 for this feature

[Marsdy]

Disappointingly I've just discovered plugin migration isn't working for the AU version of Kontakt! Was hoping to go from version 7 to 8!

Please can you implement this VSL?

[noiseboyuk]

It's very nearly the 1 3/4 anniversary of VSL not bothering to respond to any of their customers about this critical-yet-modest feature request!

How are you all planning to celebrate this?

[Andreas8420]

Hi all! Yes, this is an important feature, and if everything goes smoothly, it will be implemented with one of the upcoming VE Pro updates! Thank you for your patience. 🙂

[noiseboyuk]

@Andreas8420 said:

Hi all! Yes, this is an important feature, and if everything goes smoothly, it will be implemented with one of the upcoming VE Pro updates! Thank you for your patience. 🙂

That's great news. Thanks!

[Aaronbrownsound]

Big +1 this request! Upgraded to K8 and looking at my template with 5+ hours of manual "save as multi", swap, "load multi" clicks for hundreds of tracks is staring back at me.

Any rough ETA for the update? If it's months away I'll bite the bullet, but if it's soon-ish I'll hold off for the automatic magic 😊