Magic Russ Posted January 25, 2019 Share Posted January 25, 2019 I have a lot of projects with instances of Kontakt 5 loaded (and a few with K4). Over the summer I will probably take advantage of the sale on Komplete upgrades and will find myself with Kontakt 6. I remember hearing something about a feature that would let you replace older versions of a plugin with newer versions. Did anything ever come of that, because it might be nice if I could effortlessly replace the K5 instances with instances of K6. Link to comment Share on other sites More sharing options...
Jim Hurley Posted January 25, 2019 Share Posted January 25, 2019 Perhaps you are thinking of 'Replace if Possible on Project Load' in VST3 Migration in the VST settings of preferences? That won't help here. Oddly, while the Kontakt 5 VST is named 'Kontakt 5.dll', Kontakt 6 is just 'Kontakt.dll'. Likewise, the new executable is just 'Kontakt.exe'. Perhaps you can make a copy of Kontakt 6's DLL and rename it or use a symlink or some such trick? The older Kontakt 5 8 and 16 out DLLs are also now merged into the single new one. Link to comment Share on other sites More sharing options...
Magic Russ Posted January 26, 2019 Author Share Posted January 26, 2019 No, what I was thinking of was VST Persist Compatibility (VPC), which would have been an extension to VST3 standard, etc... http://forum.cakewalk.com/VST-Persist-Compatibility-VPC-m3408323.aspx# Supposedly this is something that both Logic and Reaper handle. Link to comment Share on other sites More sharing options...
scook Posted January 26, 2019 Share Posted January 26, 2019 VST Persist Compatibility must be implemented by the plug-in manufacturer it is not something Cakewalk can do for the plug-in manufacturer. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now