Welcome to the vsti enable midi out bug....
Here is something that happened to me yesterday..
Project with 3 Midi tracks.
One is a simple instrument track using session strings (midi is recorded in PRV)
One is a simple instrument track using lounge lizard (midi is recorded in PRV)
One is Jamstix 3.5 using enable midi out to trigger Addictive drums. (Note : Jamstix used to host drum synths, now it uses built in drum maps to trigger drum synths using midi out, so I am forced to use enable midi out for Jamstix)
Everything works great, I mix, I re-mix I get things sounding just like I want. Then I decide to extract the audio to a MP3.
Now comes the fun part, every time i listen to the extracted audio there is a weird high pitched sound happening through out the song. What could that be, hmmmm, sounds kind of rhythmic, I wonder if maybe midi channels are cross firing again...
I investigate and finally determine that for some reason, and only during audio bounce, not during playback, the midi from Jamstix is triggering session strings.
Of course that should not happen because I make sure after I am finished recording midi I always select 'none' on the midi input to these tracks. So nothing should be triggering these tracks, and even if I do not select 'none', I certainly do not select Jamstix as the midi input. And why only during bounce and not during playback ? WTF???
Now I notice something curious, even though I select none as the input, Sonar keeps changing the input to midi omni of the first midi controller in in my midi device list. I change it to none about 5 times and it keeps changing it back to Omni and session strings keeps getting triggered by Jamstix. Hmmm.
So I then select midi in to session strings as channel 6 (Jamstix is channel 1) and problem is solved.
It seems as some level Sonar cannot distinguish in a lot of instances between controllers and channels.
I do not know if it is the same issue or not, but I do know that 'enable midi out' on vsti's in Sonar since 8.5 has been real hit and miss.
JR