Vienna Symphonic Library Forum
Forum Statistics

193,864 users have contributed to 42,898 threads and 257,862 posts.

In the past 24 hours, we have 2 new thread(s), 12 new post(s) and 88 new user(s).

  1. Home
  2. Software
  3. Vienna Ensemble Pro 7
  4. VST3 auto migration Kontakt 6 to Kontakt 7

  • VST3 auto migration Kontakt 6 to Kontakt 7

    S
    S
    last edited
    last edited
    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!!!
  • S
    S
    last edited
    last edited

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

    Nuendo auto migration k6 to k7
  • ErisnoE Erisno moved this topic from Vienna Instruments Pro on
  • N
    N

    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
  • T
    T

    +1 for the request.
  • C
    C

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

    Thank you!!
  • D
    D

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

  • mducharmeM
    mducharmeM

    +1 from me too
  • S
    S

    +1 Here as well
  • N
    N

    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.

  • B
    B

    +1 This is a much needed feature.

    Give us a sign please VSL?
  • D
    D

    +1 Kontakt 8 now makes this even more important
  • L
    L

    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.
  • N
    N

    VSL, the silence is deafening.
  • D
    D

    +1 for this feature

  • M
    M

    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?
  • N
    N

    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?
  • Andreas8420A
    VSL Team
    Andreas8420A

    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. 🙂

    VSL Team | Product Specialist & Media Editing
  • N
    N
    @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!