Not all the midi bug are Sonar related. There's been some age old midi bugs that have been fixed in Windows 10.

alewgro
this is STILL not fixed :(  

Basic MIDI functionality, still broken for 5 years now.

 
Please don't blindly bump all threads mentioning MIDI recording/echoing problems without reading through them very carefully. In this case, see my post #20, and the OP's post #24. This issue was not related to Silktone's bug; it was user error.
 

I thought that it was this issue:

http://forum.cakewalk.com/Finally-been-able-to-duplicate-the-Enable-MIDI-Output-bug-without-3rd-party-plugins-m1942818.aspx?high=midi+out
 
(which i found afterwards).   If not, my apologies, but the issue above still exists.

Exactly.  Sonar is NOT listening to the input device you choose until you do some crafty switching back and forth, which seriously - after 5 years still not fixed is plain embarassing.

When was the last problem report made?  I will make one myself tonight when I have time for an in-depth write and with screen shots.  I will post it here.

Doktor Avalanche
Too much noise.

Exactly what I was hoping to prevent.    Yes, there are issues. I have replicated and acknowledged them previously, but this thread is not a good reference because there was user error and misunderstanding complicating the issue, if not completely accounting for it.
 
EDIT: Also, the alarmist and non-specific nature of the thread title is not helpful to begin with.
 
This will my last post in this thread, and I hope everyone will voluntarily let it go back into hibernation.
 
 

Good discussions.    The essential thing:  "Tracks" are nearly infinite, while "Channels" fall into the Midi standard, only 16.      Still in the very latest Sonar Platinum there are things that treat midi channel as a meaningful thing, forgetting that we work with hundreds of tracks.

.

Spencer
I used to have that weird MIDI crosstalk thing, but not anymore since I raised the midi buffer to 1000 for some reason.

 
Over the many years of dealing with the MIDI crosstalk bug I tried everything, including setting every buffer I can find to their extreme values. Nothing worked accept the partial fix that Noel did in X3d. It is possible that you had a different workflow from mine, which might explain the discrepancy.

williamcopper
I read all this before realizing it was an old thread.   I do not have any of these problems, but I do three things that might help someone with them:  

OK...

williamcopper
  no midi echo;

Since MIDI echo is what makes a software or hardware synth react to the controller as it is being played I'm not at all sure how you can manage without it. Seems kind of essential to me.

williamcopper
no "omni" setting;

"Omni" has its uses. One example is a beginner who, perhaps knowing little about MIDI, just wants to plug in a controller and have it work without worrying about MIDI channels. Omni can also be useful when recording MIDI controllers sent by a multi-tymbral synth that uses a seperate MIDI channel for each voice.

williamcopper
no midi out from any VSTI synth. The last one might be interesting to mess with one day, but it seems to me to be easier to get layering of sounds in other ways. 

MIDI out from VSTi's is something many of us were flagging up as a serious omission for years, and later, when it was supposed to work and didn't, major bug. As well as allowing e.g. a third-party VST sequencer to control one or more VSTIs in the box it also allows for the use of vst programming plugin and control interfaces with external MIDI hardware such as real synths or guitar multi effects.

There is more to life than software synths and samples. The hardware synth market is pretty big at the moment with new models and reissues of old synths coming out all the time. If Sonar doesn't make it easy to work with them then that'll be a pretty hefty chunk of the market closed to Cakewalk.

+1 for next update.