Vienna Symphonic Library Forum
Forum Statistics

190,125 users have contributed to 42,709 threads and 256,992 posts.

In the past 24 hours, we have 4 new thread(s), 14 new post(s) and 39 new user(s).

  • FR - Automigrate Kontakt 4/5/6 to Kontakt 7 AU and VST2 to VST3

    last edited
    last edited

    ear 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 template or song will load with Kontakt 7 instead. Same goes for AU (Audio Unit)

    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!!!

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

    [img]Nuendo12_Kontakt-5_to_Kontakt-7_auto_migration.png[/img]

    I have a meta frame that I used when working with Jóhann Jóhannsson that I wanted to update but unfortunately all ist lost now. On the Apple Silicon Macs is no Kontakt 5 installed. Manually swapping K5 to K7 would mean empty instances without anything in them!


  • +1 Really need automigrate feature on VEP

  • Hi, 

    Just a quick thumbs up. We hear you! 

    This has been on our list for quite a while now... and we really thought that NI would stick to their prediction to keep "Kontakt" as instrument name for upcoming versions after Kontakt 6 (instead of adding numbers again).

    Best, 
    Paul 


    Paul Kopf Product Manager VSL
  • last edited
    last edited

    @Paul said:

    Hi, Just a quick thumbs up. We hear you! This has been on our list for quite a while now... and we really thought that NI would stick to their prediction to keep "Kontakt" as instrument name for upcoming versions after Kontakt 6 (instead of adding numbers again). Best,Paul
    Yes very annoying. There was a very weird debate going on in the kontakt beta forum and I was so upset about some responses. Anyways. Do you think the auto migration feature can be implemented? According to NI it should be easy to implement for AU and VST! Best, Sam

  • Hi Sam, 

    My experience is that most things are indeed possible in software. 

    Now, "easy" is a word developers usually us BEFORE they start working on something, or if it is a task for someone else....

    So: I hope we will get there, it is definitely on our list. But I can't make any promises. 

    Best, 
    Paul 


    Paul Kopf Product Manager VSL
  • BenB Ben moved this topic from Vienna Instruments Pro on
  • Just wanted to check the status on this. I haven't been able to load most of my old projects. Manually replacing the plugin doesn't always work becuase some of these have custom assigned midi learn CCs that can't be even known, much less reassigned, without loading the old version.

    Cubase apparently has this ability already, need it for VEPro...

    @Paul said:

    Hi Sam,


    My experience is that most things are indeed possible in software.


    Now, "easy" is a word developers usually us BEFORE they start working on something, or if it is a task for someone else....


    So: I hope we will get there, it is definitely on our list. But I can't make any promises.


    Best,
    Paul


  • Hi Paul and the whole team of VSL,

    Could you please give us an update on this feature? Is it still in the works or have plans for it been shelved? Native Instruments have created problems with updates for certain instruments breaking backwards compatibility. The newest version of NI Noire doesn't work with Kontakt 6 anymore, for example. If you update, all our old projects won't load Noire anymore. That's why this feature would be all the more appreciated.


  • For those we need to save a copy of the older version, say with "K6" appended to the name.


  • Anyone found any workarounds for this?
    Pro Tools 12 Mac Pro VEP 7