stand alone kontakt 2 not receiving midi data

Kontakt 2 is completely unresponsive to my midi controller. Before you say "RTFM idiot" please read on. I have enabled EVERYTHING in the midi in/out under the audio/midi dialog, midi ch is set to omni and yet I not only hear nothing when pressing the keys, the Kontakt 2 CPU and Disk indicators at the upper right of the UI are inactive. It's as though my keyboard is dead.

However, I have no trouble triggering samples using the Kontakt 2 UI keyboard and no trouble using the midi controller with Kontakt 2 as a VST instrument. My midi controller also works with Reason in stand alone mode. Clearly Kontakt 2 works and clearly my midi controller works.

Please help.

Many thanks.

 

You say you have enabled "everything" in the MIDI in/out dialog box. Try enabling ONLY the controller you want to use.

 

just updated to komplete 5 and I have the same problem with no midi input with K3 . And yes I have the inputs turned on in in midi set up . I even turned them all on. this is with my pc88 in my motu micro lite usb midi interface and directly with my usb novation remote SL controller. I also tried only specific controllers turned on. All connections are fine in OSX midi setup when tested. Funny thing is now kontakt 2 doesn't work with midi input either although it worked a few days ago . However all other NI products Absynth4,E. Piano,Pro-53,Massive, EW gold kompakt player all work fine with midi input and they are all set up the same way. I just installed the 3.01 update and didn't help.This is in standalone . Now I tried it DP5 and as an audio unit I can play K3 with midi input. Any other ideas? I'm not getting much music done today.

G5 2x2.5
OS10.4.10

 

Yikes. Sounds pretty bad. I am using K2 only at this stage with DP so I can't help you -- sounds as though you've done a lot on your own already.

John

 

fortunately K2 and K3 are working in Dp as AUs for me . I was just trying to get know K3 a bit in standalone.

 

I feel like an idiot. I rebooted my PC and everything was fine. My guess is that Kontakt has a driver communication problem. I am sure you guys tried rebooting. If not, might be a good idea.

 

I've noticed that the midi controller (I use both a keyboard and an e-drum trigger module) has to be turned on after Kontakt has been started in order to be recognized. I'm using midi ports (ie not usb) so not sure if that has anything to do with it.

 

That's interesting. What do you mean by 'recognized'? As I said, Kontakt can see the midi controller it's just that Kontakt does not receive or recognize any midi data sent from the controller in stand alone mode.

Is that what you mean?

 

What I meant was that if I start Kontakt and the midi controller is already on, pressing keys (or hitting drum pads)doesn;t cause any activity in Kontakt. I have to turn the keyboard (or the drum brain) off and then on again and then Kontakt responds to them.
I seem to remember in the early days of midi this was often required, kind of a handshake between the hardware and the software. My equipment is from the early days of midi, so this may not affect you if your controller is newer.

In other words, in response to your "I'm an idiot" posting I was suggesting to "reboot" the controller rather than the PC.

 

That's what I thought. Just making sure I understood you. I will try power cycling the controller next time I run into this.
Thanks