What MIDI Issues Could Be Causing This Problem

I found that some synths and some instruments within multi-timbral synths (Kontakt), are natively set to react to fader changes on their Master Volume parameters, and I generally go in and alter that default to sever that connection.
 
I see it in quite a few of their synths and instruments. and it is pretty annoying.  I have had other synths inexplicably have pitch tied to mod wheel, and the Sonar default to zero all continuous controllers would jazz that up unless I altered that default behavior for that synth.
 
I offer the above to just illustrate that there may be some sneaky ways things can happen that do not involve recorded midi events.
 
Bob Bone
 

OK! I just now Disabled the Volume in the most problematic track, and before I checked back here I had added a Controller 7 msg to 2 keyboard tracks that are supposed to be at the same volume.  One of them worked as it should, but the one that's been problematic worked a few times on playback.  However, after that it started doing the following:
I had set the Controller 7 value at 55 for both tracks.  The UNproblematic one worked fine, and still is.  The problematic one started jacking the volume on the keyboard up to 80 BEFORE it even got to the point where I had set the Controller 7 event (measure 11). Then, as soon as it would get to measure 11 it would tick down to 79 on the keyboard.  So, it's OBVIOUSLY responding to Sonar, but still has a mind of it's own.  If I could just get to the place where I could mix it down to audio I would, but I've got to get another whole section done before that.
 
I'm going to send this post to the Sr. Alesis Tech Support guy that might regret reaching out to me before it's all over with.
 
Thanks Guys,
KC
 

You can try to get from http://www.tencrazy.com/gadgets/mfx/ 2 plug-ins: PortDiag and TrackDiag.
Insert both on MIDI track in question. One display if something going into track (from MIDI input), other display what is the output from that MIDI track. At least that should show what SONAR sends.
 
For example, controller 7 events are also sent by Track Volume Automation.
 
Excuse me if I look in wrong direction, noob here

Yes, these plug-ins are MIDI FX.
 
Do not be confused that events are shown in a kind of "reversed" order (first events are at the end of the text). But I guess you are just interested either you see some CC at all and either they come from the input or somehow generated at track level.

Hi King Conga...
 
Also check to make sure you have not accidentally/inadvertently sent a
volume controller to your keyboard via system exclusive msg 
along with your patch changes..
 
You can use Splat's midi filter prefs to check this.
 
Hope this helps,
 
Mel  

King Conga
OK! Azslow3, I installed those plugins and here are the results.  The Port Analyzer didn't show any data.  However, the only data the Track Analyzer showed was at Bar 1, and they were Cntrlr 64, and the Program Change that is the same ones set in Track View, and finally, the expected Note Events.  All of which were also found in the Event View. 
 
Here's the odd thang.  The Volume jump happens not only at the beginning, but also at bar 11, even after I turn it back after the initial jump.  When I substituted the Cakewalk TTS synth there was no volume jump.

So, it looks like that is not sent from this track.
 
But have you checked that some other track is not doing that? I mean if you solo only this track, does it still happens?
Also check Control Surface section for correct output settings of all CS plug-ins (if you have some).
 
My logic (can be wrong): till you send MTC, Alesis has no chance to know "that is bar 11". You have checked one track and it send nothing related. I have not seen that Sonar generate any signals "hidden" and on its own, so something send it at bar 11. Either within Sonar or outside (if you use some intermediate MIDI processing devices/software).

King Conga
OK! Azslow3, I installed those plugins and here are the results.  The Port Analyzer didn't show any data.  However, the only data the Track Analyzer showed was at Bar 1, and they were Cntrlr 64, and the Program Change that is the same ones set in Track View, and finally, the expected Note Events.  All of which were also found in the Event View. 
 
Here's the odd thang.  The Volume jump happens not only at the beginning, but also at bar 11, even after I turn it back after the initial jump.  When I substituted the Cakewalk TTS synth there was no volume jump.
 
I'm fwding these findings to Alesis, but please let me know your opinions.
 
Thanks,
KC

Perhaps you can determine what midi events are common to the places where the volume jumped, as it might be possible that a midi event  triggers ANOTHER non-recorded occurrence - such as what happens with certain synth, and even certain instruments within a certain synth, with regard to Key Switches and that sort of thing.
 
The fact that it does NOT occur when you use a different synth is consistent with the above.  I had to alter several of the Kontakt factory patches, to change the note assignments to put the default key switch notes down to a note level below where I would ever try to play the notes on my mid keyboard.
 
Key switches are used by all kinds of different synths, to allow extremely variant articulations for many instruments, such as Kontakt 5 - a lot of string presets have keys set up to change things about how the sounds are played, to dynamically allow someone to change the bowing technique, such as legato or pizzicato, or for organ patches, where different upper and lower drawbar settings are instantly realized by hitting one of many key switch notes - going from a nice flute-like clean soft organ sound to a growling snarling Deep Purple John Lord Lazy sound.
 
You might look to see if the synths having these weird changes are responding to these key switches - for me, I have to click on a little keyboard icon for Kontakt to get it to display the keyboard at the bottom of a loaded instrument in a multi-rack.  You will see any assigned key switches because they will be a different color than the regular playable keys.
 
So what I did to 'fix' my playability problems was to change any key switch note numbers to be out of the range of keys I would likely be playing for the instrument.  Than I would save that instrument.  I can still use key switches, but now I am not accidentally changing instrument articulations while trying to rock out playing.  :)
 
I HOPE the above helps get this figured out.
 
Bob Bone
 

OK! I'm back.  I had to take a break from this thing, or else I was going to break it into a 1,000 pcs.
So, I've discovered 1 more critical piece of info that I think you 2 touched on.  When I solo the Problem track it's NOT a problem.  Levels stay where they should.  The TrackAnalysis still doesn't tell me anything more than what the Event log tells me.  Now, here's where I'm pretty confused on what you guys are instructing me to do.  My problem, not yours.
 
I was going to start soloing other tracks, and monitoring the Problem track on the 8HD to see if, and when the jump occurred.  However, I wasn't sure what, and how I should do with the other tracks.  Meaning, do I solo just 2 tracks... the Problem track, and any other track? But considering the Problem track doesn't give me problems when it's solo'ed, how am I going to know which other track is the problem.  Follow me?  So, that's where I'm confused... REALLY confused as to how to proceed troubleshooting.
 
Again, I'm going to fwd these findings to Alesis, along with the actual file.  BTW, I guess it wouldn't help if I uploaded the file would it?
 
Thanks,
KC

Thanks much for your patience Azslow.  Will keep you posted.