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!

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.

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

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

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.

Bristol, I heard you the first time. I need to assume that way to check lane automation data would be to check each track and buss to see if it has an envelope bar... if no bar, I assume there can be no automation.  Perhaps I am incorrect in this assumption.  If so, how would one check data on the lanes.... meter changes, tempo changes and or set points(or markers whatever they are called) are all null past the last musci data (audio or MIDI) on my projects that don't stop.

Jim

Noel, so much debate on this topic.  And this topic came up several times before

Isn't it simple just to implement a stop at the end of a project, or region like in PT HD?

I can't imagine how hard that would be?

sincerely

dan le

I wholeheartedly agree.

Way late to the game, but experience this problem occasionally.  As to the OP's post... I'm going out on a limb here, but in X2 this is a matter of simply selecting "Options" above the track view and selecting "Stop at end of Project".  if it doesnt stop where you believe it should (extending reverb tails, removing excess track data... whatever) then adjust your length.  I think this is the easiest solution if I understand the CRUX of his issue. 


I would have never posted this (being an old post) but I hate it when I ask for help, only to be reminded to Search for it... then find threads like this, that really seem to never get to the easy answer.

Tom

Sepheritoh
I am on X2 (64bit). Under certain circumstances, Sonar will not stop at the end of the project and continue to play for another 4 or 5 minutes. This is an irritating bug, and a search on this forum has once again confirmed that it is a know bug for a long time and has been reported to Cakewalk many times. The fact that Cakewalk is not interested in fixing it has caused them, and me serious business. I checked my option stop at project end is ticked and there are no midi events or automation events after the real project end.
 
And now for the long and winded story. Names places and story details have been changed to protect the innocent.
 
I have been bugging a big time engineer friend with a big time studio (and a wall full of gold disks) a long time to throw some work my way, which he has kindly done. I've done some orchestrations for some of his projects. Most of the time pretty successfully. Well, Mr big-time-engineer uses that other big-time-DAW that some people consider the industry standard. Needless to repeat I use this non-industry-standard DAW called Sonar. Mr-big-time engineer has this big-time-client who wanted some orchestrations done, so Mr-big-time-engineer threw the bone my way, who did this most beautifully job. The whole job was done in Notion 4 (another not-so-industry-standard-I-know) and Sonar and rendered down to a big wav. After a night-through-no-sleep session I am done. With pride in my step I walked into Mr-big-time-engineer's studio, with the big-time-client anxiously waiting on Mr-big-time-engineer's leather sofa in the back of the studio. I handed the CD to Mr-big-time-engineer, who duly pop in said CD into computer and copied the wav file into the project for listening pleasure of  the big-time-client, casually questioning me "Why is the file 5 and a half minutes. The song is only 3". Feeling a little confused I had no answer to offer, which was OK then, as Mr-big-time-engineer started playing the song for the big-time-cient, who giggled of pleasure upon hearing the results. The big-time-cient immediately demanded a copy of song on CD to play for the producer, sponsor, friend, mother, and any other random persons he would convince to listen to it. Mr-big-time-engineer duly complied to request and burned project to CD. Upon investigating CD before handing it to the big-time-client Mr-big-time-engineer suddenly let go of one load and ugly swearword. "This song is 5 and a half minutes. What is wrong here" or something similar with a few extra F words. Then Mr-big-time-engineer looked at me and asked THE question: "Eric, are you still using that ......... software? If I remember right this has been a problem with Sonar for a long time. When are you going to move over to a professinal DAW?"
 
OK, needles to say, Mr-big-time-engineer had to save the day by burning another CD and the big-time-client could not stop laughing. Finally commenting something like "If you want to play with the pros you have to start playing like a pro" before leaving.
 
Needless to say I felt like a total donkey and probably lost out on a big break. Mr-big-time-engineer has many other orchestrators to call upon. I embarred him in from of a client, something that will not be mentioned again, but remembered forever. The big-time-client will probably never ask for my services again. At the end of this story I die in a gutter, a forgotten genius artist with no penny to spare.
 
Cakewalk. When are you planning to solve this problem?

your big-time-engineer appears to suffer from histrionic personality disorder. 

GMcT
The simple fact that this "fully featured professional DAW" has no end of project marker is a really basic oversight.

 
There's a difference between a "fact" and an "opinion." Here's a fact: on October 3, 2015, you posted a thread titled "Goodbye Sonar, I've had enough." In it, you said:
 
"So, I'm going to return to being creative in what I view as a technically inferior program but which is far more user-friendly and has a vastly superior interface/workflow.

Goodbye Sonar, it was a real waste of money, but that is something you can only find out by paying for it and trying it out."
 
Yet here you are. Either you're still using SONAR, which means the thread I referenced above was just meaningless grandstanding, or you're not using SONAR, in which case I can't help but wonder why you feel compelled to continue posting here.
 

The fact that you have to select what you need to be rendered in advance, is an extra step that professionally speaking, should not be required.

 
A true professional knows you don't always render an entire project. SONAR currently lacks the psychic powers required to read your mind and determine in advance which portion you want to render, or whether you want to do something like render a particular passage of a virtual instrument. Granted, maybe someday you'll be able to say "Cortana, please render the section I remixed between measures 22 and 36, then drop it in place of these measures in the previous mix" but we're not there yet.
 
 
 

Anderton
Granted, maybe someday you'll be able to say "Cortana, please render the section I remixed between measures 22 and 36, then drop it in place of these measures in the previous mix" but we're not there yet.
 

"I'm afraid I can't do that Dave. This conversation can serve no purpose any more."

Man, imagine if we'd had internet fora when ADAT was a common recording platform. Some of you people don't know what suffering is, I swear.
 

Noel Borthwick [Cakewalk]
... best practice when doing a final render is to explicitly select the region between the start and end point you want as well as all relevant tracks.

To simplify this process I add explicit markers called begin and end to the project. Then when its time to export I do this:
- open the markers view
...
-  Click the begin marker in the markers view
- clrl-click the end marker (this selects only the region that you wish to render)
- export
...

 
So Cakewalk already has an "End" marker available, but it is not associated with any default automation and we have to type in the label every time. I recall seeing this topic come up repeatedly over the years. Why not add a little functionality to help with this?
 
I could see having the "add marker" dialog redesigned to have an option to select "*Begin" or "End*" markers or to type in user-defined markers. With a bit of engineering, it would then be possible to design "*Begin" and "End*" be special markers that can be used in automatic processes. Maybe these special ones can also typed in (with code to prevent duplicates).
 
Then make these specific markers act as internal hooks for default behavior during render process. For example: 
[IF *Begin and End* markers are both present, THEN select that range for rendering and ask for confirmation with a dialog box that displays the default times of these markers and gives options to move those markers or to select the entire project],
OTHERWISE
[ask the user to define the range to export using a dialog box that defaults to selecting entire project but gives option of setting *Begin and End* markers before rendering].
A good user interface engineer might come up with a better way to get this done.
 
Until this gets built in, I'll be joining the group that now knows about using manually inserted markers for this functionality. Thanks for the reminder.

i hope this has been resolved for some of you but was confused as from pro audio days you can make sonar stop at end of project by an option setting. it is found on arrangment page under option and last entry on drop down