How to fix Komplete Kontrol VST2 after 3.0 update ?

JesterMgee

https://community.native-instruments.com/discussion/comment/161057#Comment_161057

Well, that is the solution which you need to do one of 2 things to resolve:

• Understand the issue and do the required preparations before doing any updates
• Stick to the version that has VST2 and never update.

The issue is really lack of preparation and understanding of the problem as this has been discussed around forums for 10+ years now way before it was an issue like it is now.

Mac users are the ones that really need to be up to speed because the OS and compatibility with software is constantly changing. Before blindly updating anything, questions should be asked or at the least, backups should be made.

The solution for this issue, which I have posted probably 600 times now is both above and regurgitated again here:

https://community.native-instruments.com/discussion/comment/161834#Comment_161834

You install the previous KK version that has a VST2 plugin option and if you are on macOS you need to launch your DAW in Rosetta mode. You then do as detailed and work through each project and try swapping out the VST2 for VST3 instances and if you dont know the preset sound you used, use the plugins export option… this only will be possible sometimes as some developers only offer VST3 options with a new plugin version that is sometimes not even compatible with older presets.

It's a mess and it's one of the reasons I stick with v2.9 of KK and use Windows for my work because it's not an issue at all, for mac users tho, no hope in sticking with anything, you are always forced at some stage to update and fix things.