EDIT: Was: Fast bounce ignores reverb? Now: Fast bounce and Freeze note-offs!

Hmm ... this might be more complicated.    After doing a slow-bounce on the same material, then trying fast bounce again, the aux track effect was present in the bounced material; however one of the notes was abruptly cut off.  
 
Ok trying to track it down further:   tried a "freeze" of the material going to one of the vsti's.    Same note abruptly cut off, in freeze, but sounds normal in regular play.   Using slow bounce, audible, it sounds normal.
 
Further edit: reduced everything to two midi tracks, two notes, one VSTi, two outputs.    Same problem in freeze and fast bounce: the note on one track is cut off by the end of a note on another track.    This does NOT happen, same two notes, same tracks, in slow audible bounce and does not happen in playback.   
 
This is using GPlayer as VST instrument, two outputs.    I tried replacing it with Kontakt 5, two outputs, and the freeze worked correctly.   (However, I believe there have been problems with Kontakt in the past...)     I wonder, now, if the latest Kontakt may be more protective of bad output from Sonar during freeze?   Otherwise, why would GPlayer work one way during freeze and a different way during playback? 
 
 
 

This likely specific to that synth. Note on's and note offs are matched by SONAR. There was an issue with the counting that was fixed in Dorchester or Cambridge if I remember. 
i.e. if you send 2 note on's for the same note and MIDI channel, the note should NOT stop sounding until the last note off has been sent to the synth. Some synths respect this counting and others do not. So they may stop sounding when they receive the first note off.
You can verify this by making a test track that has a long note and overlap a shorter note (same note number and channel) with that same note on the same track. Check if the synth sustains the original note or cuts it off when the short note ends.

Thanks for the replies.    It's peculiar.   Still working on it.   May not be related to "note-offs" but rather to memory access allowed to the plugin.   Now I've managed to make the early cut-off come before the other track's note.  ...
 
 
 
 
 

Downloaded the G-player demo to experiment, but it doesn't seem to have installed DLLs for the 32-bit or 64-bit VSTi anywhere - only the standalone executable. I checked both the non-default VstPlugins paths I gave it, and the paths it defaulted to. Download page says the demo includes the VSTi, so I dunno... Will take another look later.

Why? Why is it something in Sonar? Why is it ALWAYS something in Sonar?
 
Properly diagnose first before pointing fingers. Did you look into any of the synth settings that may cause the note cut offs? It almost seems like by fixating on this you are making the problem worse. I could never work like that. I'd rather get things quickly sorted in an acceptable way and get the bloody hell on with it.
 
Sorry... it just seems like picking at scabs.
 
BTW... they released an update to Foxboro to solve that Fast Bounce quirk AFAIK. Check your account. Going back to Braintree won't help because after the Bakers look at it they realized it had been there since X3... or so I've read.
 
TMYK
 
*rainbow.gif*

Beepster, you make some good points, and some bad ones.   So far I have not been able to find an "acceptable way" to get on with work, other than slow bounce with audio.   I guess it's one more in a long long string of work-arounds.    
 
I'm sorry if my post seeking answers, help, or fixes, seemed like pointing fingers.    Fwiw, I invested about 5 hours (again) in sonar troubleshooting; whether it is solely sonar, solely gplayer, or somewhere in between I still don't know.