I keep saying- the MIDI is not working properly. I have Addictive drums Midi and Audio channel on 2 tracks, and Kontact Midi and Audio channel on another 2 tracks. Addictive drums receives from Controller keyboard only (not omni, not "all"- set to Novation Launchkey Ch.1). Output in to Addictive Drums, which set to Master. Kontact set to receive from Launchkey Controller and output- in Kontact which outputs to Master. Unrelated instruments. I am on the MIDI track with assigned output to Kontact but it plays Kontack and Addictive drums. I keep saying- it is leaking MIDI data in to other tracks- nobody believes me. I do not know if Kontact instrument has MIDI out in itself. I disabled MIDI out in the synth rack options. There is no reason for it to do this, but I keep hearing drums playing and it would not go away.   

And now- restarted Sonar and it is normal. Almost 5 in the morning...

I keep saying- there are a million and one bugs in Sonar that appear and disappear for no apparent reason. I used to report on the strangest mishaps that were never reproducible and seemingly only present on my system. Usually a relaunching of Sonar, harddrive defragging, clearing of caches, or simply time itself would fix them... at least temporarily. A few, however, persist.
 
Whether Sonar, my system, or a combination of so many binary instructions being processed each nanosecond, is to blame, the world will never know.

I would say, I have had some odd things occur in x3e with audio features/output masters turning on me, and some times sonar open windows changing on me, and things undocking by them selves...tracks disappearing, again on its own,as I was playing back a track with a added plugin.
Mouse was in use to click the play button soooo not sure what might of occurred in that instance?..took forever to  get all those track views back...but it did play all tracks...must of been some kind of "hid all other tracks feature" that got twitched the wrong way with the plug ins use?.....Any hoot...after installing Platinum, and opening a x3e most recent project, (which I thought was fixed up after that ordeal was sort of solved? to play back and all tracks showing) I also notice no play back when opening it in platinum.
The bit rate was not right in the preferences...and the audio play back did not work again...so, yes the same thing is still showing signs here of odd...audio outputs not correct set to saved selection of a project that should of had that resolved...(but I have two of the same devices hooked in tandum to gain more tracks, but the INS AND OUTS are kind of labled the same 1-16, and 1-16 )....I thought I changed device in out naming scheme to that in the template being used, and sorted it out before making this project....Guess something is twisting things somewhere?
 
So..I am watching out and will keep you posted if I find out what could be doing this on my end.???..You keep checking on yours...Perhaps something with other drivers or something in MS updates has us selectively under some spell.?
 
I am going to go through these same template making ordeals, and setup the prefs again, and try renaming my ins and outs in sonar platinum...and see what fips.
 
Regards!

Getting back to the OP's specific issue...

"Dysfunctional MIDI everybody is ok with"


This implies that everybody can reproduce this, who else are you saying can reproduce this and which version of Sonar please?
 
Do you have latest drivers and firmware for your interface, novation launchkey, and other controllers installed? Are you running the latest patch for Sonar?
 
What happened when you reset MIDI?
Have you checked your controllers to see what they are set at?
 
Thanks
 

These are the only MIDI related issues I am aware of (X3E):


http://forum.cakewalk.com/Solved-Flakey-MIDI-HELP-m3044754.aspx
 
http://forum.cakewalk.com/Still-some-issues-with-MIDI-crosstalk-but-now-there-is-an-easy-workaround-m2954622.aspx#2963626
 
http://forum.cakewalk.com/MIDI-pain-in-ass-m2764210.aspx
 

This sounds more like input echo was enabled on the Kontakt track while the AD track was selected. Just toggle it off.
 
I use the same basic setup as you and this never happens to me.
 
Regards,
Dan

You are definitely not the only one. Sonar has had a dysfunctional MIDI implementation for many many years already. I've complained about it here, here, here, here, here, here and logged many problem reports for it. Here is a video showing another MIDI fail. It was confirmed by two people that the new Sonar still suffers from that issue, so I plan to make a new video and log a problem report for it. The most serious of those issues have finally been fixed a year or so ago (blatant MIDI crosstalk between unrelated tracks, and a guaranteed crash if more than one VST sends MIDI data out). But it is still dysfunctional today.
 
I think your issue is closest to the one described in this thread.
 
With all the exciting and advanced new features we get with each new Sonar release, it boggles my mind that we can't get it to do basic MIDI right. I don't know of any other modern DAW that fails MIDI 101 like Sonar does. I mean, how is that even possible given everything else it can do today?

Dcumpian, thank you for the input. This is obviously what first comes in mind. Midi echo is definitely involved in to an issue but on deeper level than you describing.
 
Yes, Input echo on Kontact MIDI track was enabled. I may not understand midi echo, but to me- it has to be enabled to be able to make any sound. It is always enabled on selected track and if MIDI track assigned output to Kontact, it should trigger Kontact, and not Addictive Drums (AD). I do not go and unselect each tracks MIDI echo every time. The way Sonar used to work was that MIDI echo would get itself on when track is selected. Not sure if this function is still there.
 
You saying- "input echo was enabled on the Kontakt track while the AD track was selected."
 
No. Input echo was enabled on Kontact midi track, and Kontact midi track was selected, and it was playing sound from Kontact and AD at the same time. It was supposed to play Kontact only. How does it get an idea to play AD, and not several other plugins that were available I dont know. I also had to disable NORA arpeggiator because that thing was sending MIDI notes in to Kontact. Do not ask me why Kontact and not AD.
 
In the MIDI options on the synth rack view (what ever it is called- on the right side of the screen), there is an option saying, "Force MIDI input through..." or something in this nature. It was checked when issue was happening. So I unchecked it and it did not change anything. The input echo on each track was impossible to disable. It would only stay lit blue or lit blue with "A" on it. What does it mean, by the way? The point is- it would not let me turn echo off by pressing on it. So this is when I restarted Sonar (not computer). When it loaded back project, midi echo buttons were not active. I assume that is because I unchecked it in the options previous session that I had to restart. Conclusion: this "Force midi something" option requires Sonar restart to change its settings. When it selected, everything goes anywhere it wants. Input echo is impossible to disable. So I can say that it is reproducible- I have to try it at another time. I am not convinced that this is an issue or that it is the only issue.
 
 

CakeAlex, thank you for reply. If you asking about audio interface, Presonus 24.4.2 FireWire mixer, yes, I believe- the latest (2013 or 2014) driver is installed. Lunchkey is Novation midi controller- it is plug and play, has no drivers. I run Sonar Platinum (New Sonar).
 
I will review the threads you offered.