Forum Jump
Since Kontakt 7 is M1 native I'd love to use it.
But I am not delighted at the thought of having to recreate my massive VE Pro server template.
Any smart way to make that switch or do I have to do it manually?
N
|
|
|
|
Originally Posted by: Nicolas Laget 
Since Kontakt 7 is M1 native I'd love to use it.
But I am not delighted at the thought of having to recreate my massive VE Pro server template.
Any smart way to make that switch or do I have to do it manually?
N
Hi Nicolas -
I think the answer is 'no' - there is no easy way. I feel your pain.
NI used to name the plugin 'Kontakt' - without the version number - presumably with a view to forward compatibility. But now the number is back so it won't automatically replace version 6 stuff in a Kontakt 7 plugin. I think the brute force approach is to save each multi from within Kontakt 6 and open them within each new instance of a Kontakt 7 plugin.
More significantly - one snag which pretty much puts the brakes on for now is that Kontakt 7 is VST3 only. so it wont work with the current version of VEPro anyway. [EDIT: wait - you might be using AU..? In which case does that work?]
So we can worry about the pain of moving our templates until later! :-)
DAW Client: Cubase 12, Nuendo 12, Ableton Live 11, iMac Pro 10/20 Core, 64GB RAM VEPro Server: Windows 11, 4/8 core, 256GB RAM, SSDs
|
|
|
|
Just leave it as is. There's no advantage to having it in K7 at this point
Dorico, Finale, Sibelius, Notion, Overture, Cubase, StaffPad Win11 x64, 64GB RAM; Focusrite Scarlett 18i20 Kontakt, Bunch of VSL, VIP, VEP, EWQL Orch, Choir and Pianos August Forster 190
|
|
|
|
Thanks for your input guys!
|
|
|
|
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.