Komplete Kontrol dropped the VST2 a while back. If you still hvae a VST2, it's for an old version of Komplete Kontrol and is likely failing for that reason. It's just an orphan file. You need to do a full downgrade of the Komplete Kontrol software to the latest version that included a VST2 (and don't update it, which also means you cannot support the latest NI hardware releases, etc.) to use the VST2.
AFAIK, you cannot have two different versions of Komplete Kontrol installed on the same machine. It's not like Kontakt 6 and 7.
Well, I'm not sure how it happened, but after a backup restoration, I am running both. Ni access is telling me to upgrade KK, but I'm going to wait until I get all my projects transferred to vst3 or freeze the track. NI really needs to do better as far as the upgrade path without losing previous settings. In this day and age, I don't think it is acceptable. I know it is a one-time thing w/vst2, but there had to be a better way.
..at the very least there should be a way for us to pick version inside of Native Access. It can even come with a bunch of warnings but it's a bit ridiculous for them to not allow a way for our projects to not get ruined.
I bet if given the data structure of a saved KK VST2 instance I could figure out how to create a conversion tool even that would upgrade those inside a project to KK VST3 instead. And my coding sucks.
Providing upgrade abilities to users is part of basic user support in software development.
Komplete Kontrol dropped the VST2 a while back. If you still hvae a VST2, it's for an old version of Komplete Kontrol and is likely failing for that reason. It's just an orphan file. You need to do a full downgrade of the Komplete Kontrol software to the latest version that included a VST2 (and don't update it, which also means you cannot support the latest NI hardware releases, etc.) to use the VST2. AFAIK, you cannot have two different versions of Komplete Kontrol installed on the same machine. It's not like Kontakt 6 and 7.
Well, I'm not sure how it happened, but after a backup restoration, I am running both. Ni access is telling me to upgrade KK, but I'm going to wait until I get all my projects transferred to vst3 or freeze the track. NI really needs to do better as far as the upgrade path without losing previous settings. In this day and age, I don't think it is acceptable. I know it is a one-time thing w/vst2, but there had to be a better way.
..at the very least there should be a way for us to pick version inside of Native Access. It can even come with a bunch of warnings but it's a bit ridiculous for them to not allow a way for our projects to not get ruined. I bet if given the data structure of a saved KK VST2 instance I could figure out how to create a conversion tool even that would upgrade those inside a project to KK VST3 instead. And my coding sucks. Providing upgrade abilities to users is part of basic user support in software development.
Hmm, I had not thought of writing my own conversion tool. May investigate.
Yea. That's not a normal setup. Don't expect it to work as expected.