midi controller not working with stand alone...

hi guys?? im so lost, idk where else to look or turn. i have a digi 002 fader, and kontakt works perfect inside of pro tools, as does many of my other stand alone vst's as rtas plug ins, but when i load kontakt up, and i try to trigger the sounds using my midi controller, it doesnt work. i turn the 002 midi in port on. i use the same set up with my mini moog stand alone/vst and it works fine, no problems...wut could be the issue im having? help please. when i use the keyboard inside the software itself, i have no probelm hearing the sounds.....

oh yea, im on a 2gz intel mac book running osx 10.4.9

 

I know this may sound like the too obvious thing, but you have set the Kontakt instrument to receive on the same MIDI channel as your controller sends on? Your sequencer might have a smart MIDI thru feature, that maps the controllers send channel to Kontakt's receive channel.

 

WOW! I am having the EXACT same problem, with M-Audio's Trigger Finger midi controller. When I open Kontant in DP, it recognizes Trigger Finger and everything is fine. When I open Kontakt stand-alone, it does not recognize Trigger Finger at all. I wrote to NI and I just got a reply today saying, check your MIDI channels, etc. But I am not a novice with this stuff. My Kontakt instrument was set to Omni. My Trigger Finger was transmitting MIDI just fine. In fact, I opened Battery 3 and it was triggered 100 % correctly by the Trigger Finger, in both stand alone and as plug in. I set the Trigger Finger to hit C1, C2C3 etc. on a standard Kontakt piano, so there's no chance it was just trying to trigger an unmapped key. I checked all of the audio and midi settings across the entire system, from Kontakt to Apple to Trigger Finger, and DP and Battery, and everything is as it is supposed to be. I am convinced there is a problem in Kontakt. It simply does not recognize this USB MIDI device as a stand alone app. I have cross-checked everything in the studio to find a culprit and there is none. If I can open Battery 3 and get a hit, but can't do it in Kontakt, then Apple, the Trigger Finger and everything else is working fine - the problem is with Kontakt.

 

You mean it doesn't show in the File | Audio/MIDI setup | MIDI list of Input Interfaces? Sometimes a USB MIDI controller has to be turned on before the receiving MIDI application (Kontakt in this case). Any difference?

 

Also I've noticed K2 (and I think maybe other NI instruments) is a bit unfriendly in that whilst it will try to remember which midi inputs where turned on last time it loaded it only seems to keep a sequential tally, so if the OS order of available midi ports has changed, K2 ends up turning the wrong one(s) on. I've got used to this, (because I've got about 14 different possible midi ports, and don't have them all turned on all the time) and so check each load (and of course it doesn't apply in-DAW) but it's irritating.

One for NI: if any Mods or staff notice this thread - be nice if instruments could store the actual port names that where last used, regardless of sequential order presented by the OS.

 

so weird, i couldve sworn i was doin that last nyte...maybe i wasnt...it;s working now lol....thanx for the qucik reply...

 

"You mean it doesn't show in the File | Audio/MIDI setup | MIDI list of Input Interfaces? Sometimes a USB MIDI controller has to be turned on before the receiving MIDI application (Kontakt in this case). Any difference?"

Hi, thanks - actually, Konktakt does show the TFinger in MIDI setup, and it's set to on, along with all my other MIDI devices. I have the K2 instrument set to Omni. Battery has no problem seeing the TFinger and accepting its input in standalone or plug in modes. K2 doesn't have a problem either, as a plug in, with the same exact instrument setup it won't work with TFinger on in standalone mode. In standalone, K2 sees the TFinger but won't produce sounds. I've double, triple checked that the TFinger is transmitting on notes active in the instrument. No sound - or CPU usage or disk drive usage. So, the Tfinger midi transmission is just not getting into the K2 instrument, even though K2 sees the TFinger.

The one key difference between the TFinger and my other midi devices is that the TFinger is USB, all my other devices are on the midi interface. I am trying to explore this but not getting far. But that's what I think, a K2 bug having to do with USB Midi controllers

 

I'm not sure about your logic there. I use K2 with four USB controllers myself (actually two controllers and two interfaces); no problems.

ew

 

What if you set it to the specific channel your controller sends on? Also check, that the K2 instrument doesn't have a specific MIDI channel assignment per group in the source module.