Hi Fellas,
 
I've been having the issue of getting my project to end where I want it to like some others using Splat and until a simple way to lock the end of a project comes along I understand that I can "delete special" to clear the automation in a  project or search for the the offending automation lane or event and delete or change it to get the project to end where you want it to while bouncing down.
 
The issue I run into which is hopefully just a setting that I've overlooked in the software is that when I delete the automation in a track and let's say that I want to create a new volume automation, when I do this the end node for my new automation track is way out beyond the end of my project. The happens no matter what the track... midi audio doesn't matter.  Since this seems to be global what determines where this last node in the track will end up when you create an automation track by default by opening and  showing the automation lane in the track view? I get a volume by default after I've deleted the one that was there previously.
 
   
 
Regards
Craig

Does anyone in the group have any insight about this?

Any forum Sonar Experts have any insight to the issue I have described here? 
What determines the automation envelope length when you create a new volume automation?
When using my control surface Mackie or a mouse I can create a new automation by arming the fader. If there is no automation assigned the new one created is way out beyond the ending of my track. This is what is causing the bounce (slilence) to extend beyond the ending of my project.  What setting determines the end node position to be so far out? The envelope I'm talking about 
is a solid line not the dotted line. 
 
Regards
Craig
 

I have noticed this on more than one occasion. I assumed there was some other event (possibly hidden) that extended the end of the project and the automation continued until that event.
I also have motorized faders on my surface but I think this happens even w/o a surface.
Like you, I just selected everything past the automation fade-out and deleted it. The first time it happened I spent a lot of time looking for the bogus event but now I do not bother, I just delete everything past the project's end.
I wish the Bakers would add a simple end of project marker that stops playback no matter what and also truncates any editing, bouncing, and so on to the end marker.
I will handle reverb tails, stuck MIDI notes or other complexities by simply moving the marker if need be.