Komplete Kontrol VST2 missing after 3.0.0 update
Comments
-
I agree, but for now, Transition from older projects with VST2 to VST3 has been made more difficult than it should be for Komplete Kontrol users that have the MK3, wouldn't you agree?
It also doesn't help for Ableton users that Ableton doesn't automatically translate VST2 to VST3 instruments of course...
2 -
I hope that will change in Live 12
1 -
@Sunborn :
Yes, VST2 should be avoided in the future (wherever possible), but on the other hand please note that even Steinberg changed their minds and added official VST2 support for another year by even implementing its native support in the actual Cubase 13 release. Therefore, the article you have been referring to above (which is from January 2022) is no longer applicable. Please refer to the thread below where I layed it all down:
The link to the actual Steinberg FAQs is here: https://www.steinberg.net/cubase/faq/
Of course, the fact that Steinberg shifted their end of VST2 support one year behind doesn't automatically mean that other companies will have to do the same (like NI having already announced that KK3 is dropping VST2 earlier than expected), but many VST vendors (and their users) are happy that they obviously have more time to make their change to VST3.
1 -
True indeed, thanks for letting me know :-)
However, if i may use a metaphor, it is like a dying man in a hospital who lives with mechanical support... it is not real life. Same thing is with the older projects, if you want to keep them alive, sooner or later you will have to change their vst2 instruments with vst3. In my point of view, the sooner the better.
Or (this is what i did a year ago, for all my projects with older vst2 plugins) export their channel as audio (so i can still have the original sound), kept the midi data and use another plugin on those. 😉
1 -
You're completely right with your example. I'm also trying to get rid of that old stuff wherever possible.
1 -
Can confirm that this does not work with Ableton Live 11.1.13 in Windows 10.
And after spending an entire day trying unsuccessfully to make it work I have lost what little patience I had left with NI as a result. I am _so_ done.
3 -
@Jeremy_NI can you replicate this?
has anyone managed to make it work with Ableton Live 11? (Or even Live12)?
1 -
Yeah on Mac certainly
0 -
Nice to see its not only me?
1 -
Here is what I suggest to users in this situation, where you have to convert your projects from VST2 to VST 3:
Install 2.9.6. This works fine in ableton.
While in ableton open your project, and duplicate your tracks which have the vst2 version of KK.
in the new duplicated track, delete the vst2 of KK, and load up the vst 3 version, then open up the correct instrument, and copy over settings, and any inserts that are on the original track.
Delete the original track with the vst2.
save project.
"Do the above for all projects which have the vst2 KK in them"
Now after that, you can safely upgrade to KK 3.02 and not have to worry about the vst 2 ever again.
5 -
@rdalcroft Finally someone else states the obvious! Well done!
I mentioned this 3-4 times on different threads (i did that process on Cubase last year) but nobody paying attention!
It is so easy and simple, but they prefer to wait for updates, then uninstall everything, and reinstall again and again and then come here and complain and then mess up their hole computer and so on and so on, while they forget that the VST2 support will end forever, really soon!
But this process can take much less time from all the above!. I did over 80 "heavy" projects full of VST2, in just 2 days.
1 -
It might work fine for you, but I can't get Ableton to see 2.9.6 when I reinstall it, not even if I force a full rescan of all VSTs. So your "solution" does not work for me.
1 -
Here is a suggestion:
Try an put the KK VST2 into a new folder with in your vst2 folder, and let Ableton scan it again, This will force it to see the vst in a new location.
0 -
reposting:
I keep seeing the advice to switch to VST3 - but that doesn't work in Ableton correct? That's why we have to use the instrument rack? I did the initial update but rolled back to the 2.9.6 right away because Ableton needs the VST2.
I have Ableton 10 (Windows 10, fully updated besides Ableton 10 - but can't afford 11) and only way Komplete Kontrol works properly is through the .adg but the .adg uses a VST2.
1 -
I use it without the adg, it doesn’t need it to function, tbh I never used it in Live (although Live is not my main DAW I use it more for Max4Live sound design)
0
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 735 Tech Talks
- 3.9K Native Access
- 15.9K Komplete
- 1.9K Komplete General
- 4.1K Komplete Kontrol
- 5.5K Kontakt
- 1.5K Reaktor
- 364 Battery 4
- 817 Guitar Rig & FX
- 416 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.5K Maschine
- 7K Traktor
- 7K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators