As usual, you need to detail the circumstances of both these issues better. Personally, I have not encountered the FX tail issue for quite some time, though it has been a problem in the past. It might depend on a particular combination of preference settings (esp. Always Stream Audio Through FX), specific FX used, bounce settings project architecture and bounce procedures.
 
I'm not clearly understanding the second issue but if there is signal on the track selected to receive the bounce, that signal could easily be included in the bounced audio, depending on your bounce options. For example, if you have nothing selected, nothing muted, everything routed to the Master bus, and bounce with Source = Buses, and Master bus selected, any pre-existing audio source on the target track will be included in the bounced audio. Nothing surprising about that.

williamcopper
All in all, are we agreed that there are two bugs with rendering midi?     1) somehow the render engine stores up any tail for the selected area rendered, and plops it into the next render (unless other play actions happen between) and 2) the render uses the target track routing, even though the target track is NOT selected and is NOT part of the intended render, to affect the result of the render.   

No one... at all... agreed to anything of the sort.
 
What seems to be agreed upon is that you are bucking absolutely ALL suggestions, advice and even reality itself.
 
What you seem to be referring to is a completely DIFFERENT "issue" and sounds like some weird routing/export option choice you have managed to set up where you have hardware feeding the export while tails are still audible... or something screwed up like that.
 
But of course... it has to be a bug. It always has to be a bug... until it's proven not to be a bug... and then... it's a bug.
 
Roight?

Beepster
 
No one... at all... agreed to anything of the sort.

Frankly Beepster, I feel that's a little harsh. I think we can all agree he believes he's experiencing some kind of issue, and that no one else has been able to reproduce it.

I'm thinking "Real Time" "Audible" bounce from the main hardware outputs (or even a physically wired loopback) could do it...
 
but a HIGHLY educated and experienced individual would certainly be able to avoid such things.
 
Therefore... bug.

The tail thing is not a bug. It's the way the audio buffers have always worked. You must select a range to bounce (or export) that includes the tail. While you can tell Sonar how long a normal tail will be, that's simply an estimate. Before I bounce, I always playback the midi until the tail is silent. That's the end of my range.
 
I thought that there was a setting somewhere to dump the buffers before each bounce (or playback), but I can't find it...
 
Regards,
Dan

Not to flog a dead horse or anything, but if you are attempting to render a portion of a continuous midi track, it is simply not possible to "select beyond the tail".    And while it's understandable that the tail is there after a render is complete, it is not so great to then dump it at the beginning of a completely different render, completely different tracks. 

As much as I hate to agree with Mr. Copper this is an annoying issue to deal with. It should be fixed. That little bit of audio that can show up at the beginning of a new audio track.  

If memory serves me right, there are 2 ways of solving the tail issue:
 
1 - Toggle the audio engine before the next bounce
 
2 - Set the "Always suspend on stop"/"Always suspend on play" for FX on the project (only works for VST/VSTi, not DX/DXi though) in their VST property pages.
 
Don't quote me on the second one though.
 
I actually had this happen years ago and serendipitously ended up with an amazing delay effect at the start of a track that stayed in the final version...

I normally slip edit it out. 

I thought I was being superstitious by pressing the space bar (play) in between every bounce, but that fits with KPerry's work-around #1.