I have a midi issue that's preventing me from using any instrument in Sonar. In the past it worked fine, then intermittent and now not all all. A MIDI-OX test of my midi pads/keys shows clearly that they are passing notes to the computer. I can see a choice for the input in the instrument program, it's checked but it is less highlighted than the other choices. Standalone versions work fine.
 
I have also reverted to previous versions of sonar, no change...HELP!

Something is totally messed up again. I have NI KKS81 and NI Maschine MK3 with two instance of KK and one instance of Maschine in a project. And it's a total mess. With everything. Maschine, KK, automated track zoom unzooms the selected track, Input Monitoring focus doesn't switch, Instrument tracks containing two MIDI tracks pointing to different synths (figured out after I splitted the instrument track). Etc. Tried switching from UWP to MME for MIDI, but it didn't help.
 
I wonder if it's something with Windows again, is it Cakewalk, or is it NI? NI stuff hasn't been recently updated, so it's either 2018.08 or Windows 10. 
 
SOLVED: at least my problem. It turned out that after I plugged in the keyboard after CbB started it took the normal KK MIDI In as ACT surface MIDI input, so pressing keys on a keyboard started causing the change of the current track etc. I wish MIDI hot-plugging would've been more stable and predictable.

Thanks for your reply but it doesn't seem to be related to my issues.  DK

I'd say you have narrowed the problem down to a MIDI setup problem in Sonar.
 
That MIDI-OX test is my first choice whenever I think there is a MIDI problem somewhere in my setup.
 
If MIDI-OX can see your controller sending notes, and you can play standalone software instruments, you will probably do best by focusing on Sonar.
 
Did you already try rebooting, while making sure that your controller was connected and powered on during the boot?  And definitely on when launching Sonar?
 
Does your controller show as an available MIDI input in Sonar preferences?

Thanks for the response. I agree with you assumptions that the problem is Sonar related but it might not be caused by Sonar. What I mean is that Sonar was originally installed on m C: drive. I changed the installation to my D: drive but noticed that the re-install was loading files to the C drive as well. The download checks in Command center were all set for D; download.
 
I am open to suggestions for another installation but would like to insure that it's clean...IDEAS?

Reinstall Sonar on C.

Nope, doesn't change a thing. Can anyone give me a descrpition of the midi signal path once it is passed by the computer? As I said before the MIDI-OX sees all the notes hitting the usb bus but I can't configure anything that triggers the programs drums. UGH!!! 

You never answered abacab's question about whether the MIDI input is visible and checked in Preferences > MIDI > Devices.
 
If that's not the problem, please clarify:
 
"I can see a choice for the input in the instrument program, it's checked but it is less highlighted than the other choices."
 
What dialog/view is that in?
 

It's in SI Drumkit for example, under VST2 as well as in Battery under VST2. I can see both inputs and outputs are checked but the input choice is less than highlighted.

For now, it does not matter what the status of "Enable MIDI Output" on the VST2 drop down is. By default all synths have "Enable MIDI Input" enabled. These settings rarely need to be reviewed, the defaults are usually fine. The exception being FX plug-ins that send or receive MIDI data.
 

1. Start simple with a new project, insert SI Drums into the project.
2. Verify the synth has sounds loaded by clicking on the Drums in the plug-in UI.
3. Not sure what version of SONAR you are running but if it is SONAR Home/Artist/Professional/Platinum select the virtual keyboard omni as the input for the instrument or MIDI track (if the synth was added with MIDI+Audio tracks), open the virtual controller (computer keyboard) from the views, make sure input echo is enabled on the instrument or MIDI track then click the letter A on the virtual controller.
4. The kick should sound. If it does, the signal path is correct in SONAR and the problem lies either in MIDI preferences setting up the controller as a MIDI input device, the record settings in playback and recording in SONAR or it is outside of SONAR. Might be as simple as deleting TTSSEQ.ini from your user directory.