Genghis
I use it quite  a bit, but I pay attention to what I"m doing and how I route my tracks.  Never been a real issue.  Noticed it happen once and figured out why it did, so I actually make sure my MIDI is routed right.

Ditto.

SilverBlueMedallion
Yes, I can do the same....  but HERE is the problem.  I think I am figuring this out.   So, if I start Sonar with my keyboard UNPLUGGED, the input has no option but to go to "NONE" (which is really "OMNI"  (see:  http://forum.cakewalk.com/FindPost/3541278)
 
so when that happens, MIDI goes everywhere.   I shouldn't have to keep watching all the inputs all the time.  They change randomly.   

It's generally good practice to hook up controllers, interface etc. before launching Sonar or any other DAW.

I wonder if the inputs changing is a Windows thing. Sonar relies on what Windows tells it is there concerning controllers, audio interfaces and any other MIDI devices attached to the system. Windows has a habit of not recognising that e.g. a controller that's just been plugged in to "this" USB socket is the same controller that was before plugged into "that" socket, so Windows creates a new MIDI port for it. And then the DAW which relies on Windows telling it what's attached, sees what it thinks is a new, different MIDI port and does things accordingly.

And once in a while Windows will allocate a new ID to something that's always plugged into the same port.

Always plugging MIDI devices into the same USB socket is therefore a good idea because it minimises the risk of this happening.

Sonar can not set up a track to take input from a MIDI controller that isn't there or is there physically but Windows having given it a new "name" isn't the one Sonar expects to see. So when a project is opened and Sonar finds the MIDI routing it contains can't be accommodated Sonar does it's default thing in the anticipation that a human will come along and sort it all out.

I usually have nine or ten MIDI ports operating hardware, and I make sure all the external USB connected MIDI hardware is connected and working before I launch a DAW, and I have templates set up which make creating a new project much easier. And which saves a great deal of time by avoiding having to go through MIDI tracks and change their input and output ports.

OK a big problem I just experienced was, the volume CC7 on my FM8 softsynth kept being turned down because I had MIDI Out enabled on a different softsynth.  The reason?   Because my Midi controller hardware was turned off, the track was set to "NONE" (which actually is OMNI) which means it will listen to all MIDI traffic.  Terrible design choice.

 

In the video, I see VST scan during startup... depending on scanning settings, other plug-ins can disturb operations. So, please turn automatic VST scanning off.

I see that, but it is not changing anything, it is very quick.  Also I will need it next time I add a new VST.
 

I have already asked that question, and from your previous post the answer can not be "no". Which controllers and other MIDI equipment is enabled in Sonar MIDI  settings?
Try disable them ALL.
 
Event Viewer is not showing everything, in fact Sonar by default sending TONS of MIDI messages which you normally can not notice. Have you disabled "Reset controllers on play stop" in the Project / MIDI preferences ?
 

 
i have disabled them all.  No go.  Yes, I disabled "Reset controllers on play stop"...

It's as clean as clean can be.   If you see the video below, you can see how clean and simple I made it.  Nothing should be causing this.  I did edit the video, but just to save time for the viewer, I had to answer an IM in between doing things lol.  I didn't edit out anything in Sonar.

I was not assuming you have manipulated the video. Just in case you have not focused the parameter by mouse, it could be focused by something else, which in turn could point in some direction to understand the problem.
 
The video is not clean in respect to MIDI. And SOMETHING is changing the parameter. I do not think this something is Sonar, the only way it can do this is explicitly setting it throw automation API. But so far there was no evidence it ever did that (as long as you are not using Control Surfaces and do not have Automation lanes in the project).
 
In this particular case, I can imagine that Z3TA has a bug (which we can not reproduce because of some specific MS runtime you have... in the video, you have plenty of "bloatware" installed and partially running... do you have it on your other computers as well?). The value after the project loading correspond to the default preset, shown in the beginning of the video. Try to change default preset in Z3TA and repeat the test. Does is still revert to the same value?
 
 




 
the machine has Microsoft Office on it, yes I got an IM... i doubt an IM changed my synth parameter.     No bloatware though.   No it doesnt happen on the presets I have tried.

SilverBlueMedallion
OK a big problem I just experienced was, the volume CC7 on my FM8 softsynth kept being turned down because I had MIDI Out enabled on a different softsynth.  The reason?   Because my Midi controller hardware was turned off, the track was set to "NONE" (which actually is OMNI) which means it will listen to all MIDI traffic.  Terrible design choice.

I'm sorry but this doesn't make sense to me. If there was no controller to turn down the FM8 then there has to be embedded envelopes in the controller lanes of one or both of the tracks. WHy not set the midi channel for the FM8 to one you are not using in the project. That would help you locate the source of the cross talk, if that's in fact what's going on.

ampfixer

SilverBlueMedallion
OK a big problem I just experienced was, the volume CC7 on my FM8 softsynth kept being turned down because I had MIDI Out enabled on a different softsynth.  The reason?   Because my Midi controller hardware was turned off, the track was set to "NONE" (which actually is OMNI) which means it will listen to all MIDI traffic.  Terrible design choice.

I'm sorry but this doesn't make sense to me. If there was no controller to turn down the FM8 then there has to be embedded envelopes in the controller lanes of one or both of the tracks. WHy not set the midi channel for the FM8 to one you are not using in the project. That would help you locate the source of the cross talk, if that's in fact what's going on.

the CC 7 data was coming from a MIDI-out from one of my other softsynths... and BECAUSE I had no hardware controller plugged in, the input of my FM8 track was set to "NONE".... which actually isn't "none" at all, infact it is "omni"... so its going to take data from my MIDI-out from any synth track that might be spitting it out.  

Very poor design

rlared
First, I will agree with the OP that Sonar has plenty of MIDI bugs and things that just don't work right.  I really hope Sonar works on some of the MIDI features, particularly the step sequencer and programming drums. 
 
I work 90% with MIDI and VSTi's, but I'm not a composer so I only will have 6-8 tracks usually and not a ton of plugins.  I don't use advanced MIDI features.  As much as new features are cool, I'd prefer they spend more time on bugs and enhancing existing features.
 
However, I've also tried Studio One 2, Studio One 3, Reaper and Cubase repeatedly.  I've actually spent more time demoing new toys and switching DAWs and plugins than actually creating music, which is why I decided to reformat, bought lifetime updates, installed only the SONAR stock plugins and Komplete 10 (which I also own), and refuse to install anything else.  I need to learn to use what I have to its full capabilities, which will take years as-is!  I find the Lifetime Updates to be a relief. . . now I'm committed to a DAW and I don't have to worry about paying more to upgrade to the next version.  It simplifies my life.
 
Other DAW's will always look shiny and better, particularly when watching videos or reading reviews online.  Their features seem awesome and super useful when I watch a pro using them in a video.  I watch Hans Zimmer use Cubase and it seems like I could do the same thing if I just had Cubase!
 
However, like all things in life, most of it is just advertising and the fantasy that this new software is going to revolutionize your music making (and life) for the better.   Once you start using them, you start to notice the bugs and things that don't work right.  They all have them. 
 
After trying out other DAW's repeatedly, I always came back to Sonar because it provided the best mix of features for me.  
 
I say this only to give you some food for thought.  It sounds like you're an advanced user and you've used Sonar for a long time, so it may be the right choice for you to change.  But make sure you separate the marketing hype from reality when you decide!
 

I come to this forum quite often and do a lot of reading but I've never posted anything besides asking questions.  Interestingly, I too got caught up in the shiny new look of Studio One 3 and Cubase 9.  I work entirely in MIDI with the exception of recording my sax.  When I tried Studio One 3 for the first time I was amazed at how fast it opened and I was able to get to creating music.  But I noticed it didn't have a staff view and I really need that for reference purposes.  It's much easier for me to see something wrong in the staff view as opposed to the PRV.  I've also looked at Cubase's staff view and for me, Sonar's is better.  I know a lot of people scream about how bad notation is in Sonar but if I was looking to produce scores, etc... I'd use Sibelius or Finale.
 
Anyway, this thread was about MIDI and I can say I've never had any issues with MIDI in Sonar.  But then I'm not a power MIDI user like the OP.  I have a simple M-Audio controller and VSTs.  But I agree with Rlared, it's time for me to really learn Sonar.  I've used it for decades but in reality I've barely scratched the surface of what it can do.
 
I know this doesn't help the OP but I've been thinking about this for some time and this thread seemed like a good place to talk about it.
 
jp

Anderton
There's a reason why Propellerheads and Ableton canned their communities, and also, why they won't be the only companies to do so.

I've heard of canned laughter, but a canned community? That's a new one on me.

I only hope if they do can us, they delete my entire post count along with any other evidence I was ever here.

Much of the midi routing shenanigans would be solved if software sources were excluded from "none" no matter what.

SilverBlueMedallion

ampfixer

SilverBlueMedallion
OK a big problem I just experienced was, the volume CC7 on my FM8 softsynth kept being turned down because I had MIDI Out enabled on a different softsynth.  The reason?   Because my Midi controller hardware was turned off, the track was set to "NONE" (which actually is OMNI) which means it will listen to all MIDI traffic.  Terrible design choice.

I'm sorry but this doesn't make sense to me. If there was no controller to turn down the FM8 then there has to be embedded envelopes in the controller lanes of one or both of the tracks. WHy not set the midi channel for the FM8 to one you are not using in the project. That would help you locate the source of the cross talk, if that's in fact what's going on.

the CC 7 data was coming from a MIDI-out from one of my other softsynths... and BECAUSE I had no hardware controller plugged in, the input of my FM8 track was set to "NONE".... which actually isn't "none" at all, infact it is "omni"... so its going to take data from my MIDI-out from any synth track that might be spitting it out.  

Very poor design

You really don't want any help or ideas do you. You've completely ignored my suggestions and re-stated the problem. I know what the problem is. Yes the label should be different when it's set for omni. But there are things you can do to minimize your problems but can't be bothered. Don't waste our collective time if all you want to do is stand on a soap box and complain that everything sucks.