Thanks Noel for your input

My strategy (since Pro-Audio days), which has always been fool proof for me, is…

Select tracks and drag mouse along Time ruler adding additional measures start and end then “Bounce to Track”

Solo this new track and use the split tool to “top and tail” clip precisely where you want to, then “apply trimming”.

Insert a “clip gain envelope” set to “Gain:00db” then using nodes just before audio starts and ends, set gain to “Gain:-INF” 
Note... Using this method you can tweak fade in/out if needed.

Time consuming? Nah! Once you’ve done it a few times it’s as quick as, and you have confidence that it’s right. 

If you want you can copy/paste this clip into a new project (that’s why I use gain and not a volume envelope) with other tracks to make a full CD of tracks to master conjointly.

As for letting any “final cut” leaves a studio without having listened to it from start to end. Well that’s just playing “Russian Roulette”. 
Eventually..................... BANG! 

That is a very impressive "bang". ;)

I'm loving this thread because I really hate it when Sonar just keeps on playing... however, through this thread I have discovered the one thing I use all the time that causes my problem: I love track envelopes (control freak!). 

Just managing those better solved my problem! Thank you all!

BANG!

Use 0.5" tape. Top and tail. Problem solved.

Some of my projects never stop playing, yet when I hit Cntrl+End it goes to the end of where I want the project to stop. I've selected All and Viewed Events, but still no sign of a "dangling participle". Before exporting the project, I select All, then select my desired output range from the list of my pre-defined markers. It always works, but sometimes I forget to select the range and the exported song plays "forever"; hence; I always check the exported track before sending out any work.

gstring

Some of my projects never stop playing, yet when I hit Cntrl+End it goes to the end of where I want the project to stop. I've selected All and Viewed Events, but still no sign of a "dangling participle".

Same here. Something manifests itself internally in Sonar and after all these years, I still can't track it down. It's happened to me in every version of Sonar I've ever used, on simple projects with nothing but 3 audio tracks, to 50 track audio/midi projects.

The thing I don't like about it is the fact that my CPU is still cooking away. Sometimes I'll play a project while I'm doing something else, get sidetracked, come back 45 minutes later and Sonar is still going.

As for the original poster ... it's too bad that happened, but if you're doing something that important you must double and triple check your work. Typically you would export a mix, then do your mastering, then trimming. You would have had two chances to catch this problem if you would have followed that procedure ... but I read that some people are getting away from that and doing it all in the project because PC's are getting more powerful by the minute and can handle the load. I do it both ways, but the only people listening to my crap is myself and maybe my sister once in a blue moon. IOW ... I'd take much more care if I was trying to get my foot in the door with Mr. Big. Live and learn!

So, I too have seen this BUG but after rendering a mix, you can always load the audio output file back into Sonar or other Audio editor (use this as a mastering stage in your project and you reaaly haven't created any extra work) and clean up the extra 90 seconds of NOTHING (delete it) and re save... there ya go DONE.

My workaround to what I too consider a BUG in SONAR that has been there for a long time.  Yes, I have checked everywhere possible that there could be data beyond the end of song (project) in the time line and yes there is nothing there.  It is a PITA but not a SHOW STOPPER.

Jim

As other folks have said - normally the end of project is defined by the last event.  Ctl-End will take you there.  For me it is often an automation node.  And with X1 it was difficult to see these nodes against the dark background so difficult to troubleshoot.

However - I had two projects where there was NO visible event causing the problem.  Something in a track that was NOT VISIBLE anywhere caused the end of project to extend.   

Here is a perfect way to troubleshoot and fix (works every time):
1) Eliminate all stray automation nodes.  if you find any - delete the node and do Ctl-End to check if fixed.  If not fixed:
2) make a copy of the project
3) open copy and start deleting tracks one by one.  Do Ctl-End after each deletion to see which track is the offender.  Once you find the track,
4) Open the original project and rebuild that track by copying everything into a new track. Then delete the problem track.  This should take care of the problem.

Noel,

Perhaps when you guys automatically but Automation on a lane the end point is infinite or way out there?  I don't remember exactly when this happens but I do remember that a new behavior on a certain action created the automation envelop by itself.  But, I could be mistaken.

I will check again and see what project I have that don't stop at what I think is the end of project (even during playback - quite a few of my old projects when loaded, if I remember correctly).

Thanks for chiming in,
Jim

Guitartrek.... see my previous post on some anomoly (I forget which) that does add an automation envelop without the user phyically creating it.. I forget which behavior.. Scott G will know or tell me I am mistaken.

Jim

Sometimes Sonar will stop at what I consider the end of the project (the last event in the list "SHAPE") and sometimes it just rolls on until I hit STOP.  I have not detected a pattern of operation to inhibit or encourage this behavior.  I Ctrl End and the marker is at the end of the song.  I view the events list with every event type selected and view every track and there is nothing beyond the time marker at the end of the song. Strange.