REAPER and KOMPLETE KONTROL VST3 Plugin

Jesterman

Hello, i know this is a bug in recent Komplete Kontrol release but i have to say its rather annoying.

I created a song in Reaper last week for which was quite good if i will say so myself, I managed to use the KOMPLETE KONTROL VST3 plugin to use with my MK2 S88. It worked :), then on loading the song a few days later the song will not load at all. I realised its down to a conflict with this new KOMPLETE KONTROL VST and theres no way of fixing it other than deleting all references to the VST.

Reaper is known to be stable so is there any chance of fixing this please ? Or a workaround becuase the KOMPLETE KONTROL plug is actually really useful even if it doesnt fire up keyboard integration.

Ian

SYSTEM

Reaper 7.16 (Back install to try to solve it)

KOMPLETE KONTROL Version 3.2.1 (as part of Komplete 14 bundle)

S88 MK2 Twin Screen

JesterMgee

Not aware of this issue but have never heard of it in past Komplete Kontrol V2 versions.

Is there any error message? Is the issue (you believe) related to having multiple KK instances in a project?

Since you dont own an MK3 keyboard I would suggest deleting KK V3 and instead, install KK V2 and just use the VST3 version of that and see if you have the same issues.

https://community.native-instruments.com/discussion/17840/komplete-kontrol-2-9-6-last-vst2-supported-version

I have not updated to V3 because of a number of issues/reasons but curious if the issue you have is specific to KK V3 since the only real issue I have heard of like this is when VST2 instances of KK are loaded in a project and then you update to KK V3 which no longer offers VST2 instances.

Jesterman

HI Jester Mcgee, no error messages no, just a long indefinate hang on load of the project with no way of optining out of load other than closing Reaper.

I will down grade KK to V2 then, and see if theres an improvement. I do have multiple instances of KK for which I didnt think would be an issue but i suppose could be.

Thanks ill kee pyou posted. Ian

JesterMgee

Well, it should not be an issue with multiple instances and without a controlled test it is hard to know what the issue would be. V2 just more robust as it has been developed and stress tested for 10 years. WHile NI tote the new V3 as having a "whole new tech stack" what that says to me is it's a whole new ball game of issues and frustrations, evident with the many posts flooding the boards for the last 8 months. Hopefully V2 works, kind of always has.

Jesterman

Ok well trying to unistall v3 is the challenge- it looks like a blind delete of application is only way lol.

BIF

What version of Windows are you on, @Jesterman ?

But yeah, @JesterMgee's advice is sound. Drop back to 2.9.6 and see if your MK2 starts working again.