Thanks Old Timer,
Actually, in this case at least, the Alesis is a blessing as it doesn't use SysEx msging.  Weird, but true.
Brundlefly, I've also sent your comments to Alesis as well, but I'm not quite sure how to troubleshoot that.
Thanks,
KC
 
 

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).

Thanks again.  I did NOT solo that track, and I don't have any CS h'ware, or plugins for that, or any other devices that transmit MIDI.  My Fusion keyboard is connected directly to my Alesis I/O 26 (my soundcard interface), and that's it.
 
Let me ask you this. 1.) Does soloing a track actually solo the MIDI data, or just the sound? 2.) What if I temporarily archived the track, or each track 1-by-1. Would that isolate the issue?
 
I'm also curious, if it's coming from another track, how does the Alesis see it on that track?

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
 

King Conga
Let me ask you this. 1.) Does soloing a track actually solo the MIDI data, or just the sound? 2.) What if I temporarily archived the track, or each track 1-by-1. Would that isolate the issue?

If the track is MIDI track, solo/mute are for MIDI data.
 
So, I assume you have several MIDI tracks with output set to I/O 26, which is in turn connected to HD8. Correct me if I wrong.
 
So, all MIDI from all tracks are "mixed" together before they sent to HD8. I also assume that you set the channel on these tracks explicitly, so let say everything from Track 1 goes to channel 1. It is otherwise per event information, and if you copy something from different track (with events on other channel) the result is not expected.
 
So, you need to isolate what exactly is changing the volume by analyzing events sent right before. From all tracks which output something. And as Bob writes, that can be just normal note event with special interpretation within HD8.

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

Let say problematic track (which get volume change) is 1.
Solo 1+2, do you see the effect? If not, solo 1+3 (unsolo 2). Check again. And so on till you find the track which produce that bad effect on track 1. Only once you found it, Event log/TrackAnalysis are useful.

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

azslow3
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

Thanks for the link Azslow3. Handy:)