Komplete Kontrol integration issues with Reason

Ok,
So i decided to get myself a new Keyboard after seeing a clip from Proppelerheads reason to work with NI komplete kontrol
There was this guy playing the komplete kontrol MKII in reason and all the keull stuff.

So i got my keyboard plugged it in and trying to set it up like i Always do..
edit/prefresnces/ and add midi device.. for the keyboard i choose : Midi control (Surface) and for the knobs /wheels and all the goodies ofcourse the Mackie control..

I was ready to rock ...loaded up reason..browsed thru my new samples from the NI library with the kewll screens
and than…...trying to find the rec /stop/play buttons..

All the basic functions are blacked out i reset the divises in the prefenses like ten times nope nothing
So i started to utube the !@# out of this problem ..seems like this is a common problem that seems without solution. i thought be smart ,be like mike what the heck ill contact reason because its their software after all…. this is short what i got replying to me :

"If the transport buttons on your Komplete Kontrol is emulating the Mackie Control transport buttons, they ought to work with Reason .i should contact Native Instrument regarding this, they will know how the transport buttons on the Komplete Kontrol works!

All the best,



So this was what took me here asking....no pleeding,does anyone has a solution to this?

 

I suspect the person playing the clip was actually using a KK Mark 1 - that had MCU support

 

i wish it was..
but the MK1 doesnt have these screens where u can see ur library and it had

 

here is the utube link. clearly this is the MKII

 

Yes, you are right, I see that now - but there is something very fishy about this video. It appears to show the lightguide and screens being used with Komplete Select Instruments, but that should only work if they are being loaded into Komplete Kontrol first, and he doesn't show that happening. I wonder if they recorded the parts with the keyboard showing and screenshots of the plugins being loaded into Reason racks separately then bolted them together? It even shows Drumlab being used from KK on the screen but of course, in Reason itself there is no 'DrumLab' as a plugin in itself, it's a Kontakt library so it would be Kontakt that is loaded in the rack. Also correct me if I missed it (I did skip ahead a few times as it was boring to watch) but at no point could I see the keyboard transport being used, it's off-screen all the times I could see the keyboard. Very tricksy marketing.

 

i have the same keyboard and i can tell.. beside the basic buttons ( record/play and stop) almost everything works within reason even the scale and arp functions work. I can loadup komplet kontrol within a rack and use the browse knob on the keyboard to browse thru the library and select. and even play.. But the biggest issue is the basic buttons..i cannot seem to get those work. thats the fishy part for me

 

Yes you can, if you load them into the Komplete Kontrol plugin first - it's that which you would drag into the Reason rack and yet in the video we see him dragging in first Massive, then Kontakt and Reaktor but no KK, only when he shows the keyboard those plugins are there on the screen and the lightguide is working for stuff like Kontakt libraries, that just cannot happen if it's just the plugins being loaded so this must be being faked. It's implying a much deeper level of integration between keyboard and Reason than is the case, unless this is something they have not released yet (but the date is nearly a year ago so that seems unlikely).

 

Yes u are right. i just tried it. when i drag KK to the rack inmediatly the plugin button lights up and i can go browse
when i remove KK and t drag kontact of example it wont budge. and when i drag KK and then for example ad massive it wil work again on both massive and KK... but still no stop/record and play functions

 

Yeah that's how it should be, until MCU support is enabled at least.

 

well ive been thru almost the whole forum by now and ..am i the only reason user here? or what.. can seem to find anything that i can at least try to make the buttons function.. no love for reason users i guess

 

In the Series 2 the transport controls work differently to the Series 1, instead of outputting midi they seem to be using OSC to communicate with DAWS at a deeper level which is what enables the deep integration but this only works so far with selected DAWS. NI say they are planning an update to add back MCU support which I presume will also re-enable midi support for transport (presumably a firmware patch?) but not sure when yet. In the meantime if you really want hardware control over transport from the keyboard one workaround is to use the white soft buttons at the top of the display - these do use midi and in midi mode can be mapped to anything (that's what they are there for) - and can also be renamed in the KK midi editor to label their functions.

 

Ok,
This is something i can temporarely live with thanks! . But the video is from Februari 2018 imy guess is that the keyboard and its issue excist longer ..
How long do they need to fix this.Ill bet this is a more common Problemn than only with reason.why would they not make this a priority right know ( a year later) i cant be the only one having this issue

 

You're not - many of us use DAWS that don't work with 'deep integration' and have been lobbying NI the whole year to get this changed, that's why they have said they will, at least now they have committed to that and said it will be sometime early this year.

 

Wow ok,

That would be awesome.
No i have another thing ..seems like im talking to some one who know things
so i need to setup the Rec/stop/play function in the control editor right?.. no when i am in there it does not see my MKII i can see only komplete kontrol S-1 to 4 it doesnt mentiont my MKII is this right or am i going to have a new issue here.

Thanks for beeing helpfull by the way really apreciate it

 

Not the controller editor, the editor for the Keyboards is embedded in the Komplete Kontrol standalone app so open that and from there you can edit the assignments for buttons (create a new template first so the default one doesn't get changed):

https://support.native-instruments....ETE-KONTROL-MK2-Keyboard-in-Controller-Editor

Here's how I have it setup in mine (note I set this up for Studio One primarily, not Reason, but it does work in Reason using the midi learn - not sure if Reason has specific hardwired CC's already assigned for Transport functions - might need to look that up in the Reason manual, I don't use it enough to have bothered)

 

wow cool,

Ill have to mess with that cause im pretty new to the NI stuff.
but ill let you know how i did. iff i get tit to work

 

Yes ...got it to work.. still its a bit weird i have to oress the button twice but it works.. now hoping for this mcu issue to get fixed

 

You need it to be in trigger mode (sounds like you have them in toggle mode)

 

thank...silly me

 

but i do notice that every time i start reason i have to bind them again.. so on the keyboard they stay..but in reason they wont