Has anyone had this issue?  It only happens on sessions with MIDI tracks that have been saved and only some times....
 
For whatever reason, when I load that session back, and go to record more MIDI on an already existing track, I get no MIDI from my controller to Sonar (though the Midi input light in the Windows System tray lights up).  If I create a new MIDI instrument track, it works.  My keyboard controller triggers the sound.  
 
After spending some time on this, I found that all of the previously recorded MIDI tracks changed their MIDI input from Komplete Kontrol to a different MIDI input device.  Again, only on tracks that have already been recorded. New tracks set the output according to the settings in Preferences.  
 
This also only happens occasionally.  I cannot reproduce it 100% at will.  It only seems to happen when I'm cranky.  lol.  
 
Does this happen to anyone else, or am I the lucky one?

Is it possible that your MIDI controller didn't load its drivers fast enough before you started Sonar? 

I think John has a really good point. It sounds like Sonar isn't seeing the device at startup.
 
Dan
 

That possible, I suppose.  I always turn on my KK and wait for Windows to "beep", indicating it sees it, before I start Sonar, but I have never had this happen before Kingston.  You'd think I would have seen it sooner. Thanks.

Hmmm...well, an easy way to diagnose is wait for a minute after the beep and see if the issue persists. Windows could be downloading something in the background, or loading some other process. But it does seem like for whatever reason, when SONAR does the "MIDI roll call," KK doesn't reply with "present."

Not sure if this is the same issue -- but in recent use I've reluctantly learned to wait for the "userinit" process to complete before starting sonar after a boot or reboot.   (this is windows 7)   It used to be one good feature of sonar that it seemed immune to issues regarding immediate startup after boot, but perhaps that's no longer the case. 
 

williamcopper
Not sure if this is the same issue -- but in recent use I've reluctantly learned to wait for the "userinit" process to complete before starting sonar after a boot or reboot.   (this is windows 7)   It used to be one good feature of sonar that it seemed immune to issues regarding immediate startup after boot, but perhaps that's no longer the case. 
 

 I found the same issue, best to wait a few moments after starting Windows 7 before launching Sonar...
Jerry
www.jerrygerber.com