Anderton
I encountered the situation tonight of "select all" and having the ending extend past the song. This is no new thing, so I just selected the region in the timeline and Cut Special, including automation. But...it didn't work, which was odd because it almost always worked as expected.
 
I started looking for events, and it seems the issue of not being able to erase occurs if two nodes are in the same automation curve and located at the same time (i.e., one drops down immediately to the other, no time interval at all). They won't be erased as described above. As soon as I separated the nodes so they weren't on top of each other, delete worked as expected. Can anyone confirm?
 
 

Craig . . . I have had this issue many times, and have even tried your solution of "Cut Special", including automation, with no success. For me it seems unrelated to overlapping automation events. Usually I have an automation that turns to a dashed line and goes hundreds of bar into the future . . . I know it sounds kinda`sci-fi, but I have come to the conclusion that this happens usually in older projects (many pre- Sonar X series) being re-opened into newer Sonar versions, since I haven`t noticed it yet in projects started in Platinum.
 
Many of these older projects have hidden tracks, and when I un-hide them and look for automation data past the end of a project, there are those darn dashed automation lines again. Is there any other way you know of to cut or curtail them, or should I just live with it, like I always have done ?

Hey,   I have not read all the posts...this does sound like it could be it.
 
This issue is a pain,  but so easy to work around, so I don't worry 'bout it much,  but this has worked for me a couple of times...not sure it will always work.  When I want to export,  I hit control-A and if Sonar hi-lites way far out, I hi-lite all the midi tracks and "Bounce To Clips"  and usually a clip will shoot way out.  Then when I delete everything past the song/audio the "end of project acts normally.  Maybe that allows both nodes to get deleted. 

noynekker
Craig . . . I have had this issue many times, and have even tried your solution of "Cut Special", including automation, with no success. For me it seems unrelated to overlapping automation events. Usually I have an automation that turns to a dashed line and goes hundreds of bar into the future . . . I know it sounds kinda`sci-fi, but I have come to the conclusion that this happens usually in older projects (many pre- Sonar X series) being re-opened into newer Sonar versions, since I haven`t noticed it yet in projects started in Platinum.

 
I rarely open older projects, but will check out next time. Don't forget that a tempo change gets counted, too.
 

Many of these older projects have hidden tracks, and when I un-hide them and look for automation data past the end of a project, there are those darn dashed automation lines again. Is there any other way you know of to cut or curtail them, or should I just live with it, like I always have done ?

I don't know of any specific way, but I'm curious about why this occurrence is rare for me yet common for other people. Whatever the difference is could be a clue. Maybe it's because I have the habit of hitting the space bar when the song ends. 

Jimbo 88
When I want to export,  I hit control-A and if Sonar hi-lites way far out, I hi-lite all the midi tracks and "Bounce To Clips"  and usually a clip will shoot way out.  Then when I delete everything past the song/audio the "end of project acts normally.  Maybe that allows both nodes to get deleted. 

Thanks, I'll give that a try. 

fwiw: I've seen the same problem, but almost never use ANY automation at all.    And have confirmed often enough that there are not any 'real' events far out in time. 

The "end of song" marker would make my work easier. I happen to have content (clips) on the tracks, past the song end. I would like to keep it for future use and dont want to be forced delete/move or mute, I want it to stay there. 

williamcopper
fwiw: I've seen the same problem, but almost never use ANY automation at all.

 
See post #3.
 

And have confirmed often enough that there are not any 'real' events far out in time. 

See post #22. Next time this happens, put the project on dropbox or something and ping me. I've yet to see a project where there wasn't something (e.g., tempo change) telling SONAR it's end of song.
 

Afrodrum
The "end of song" marker would make my work easier. I happen to have content (clips) on the tracks, past the song end. I would like to keep it for future use and dont want to be forced delete/move or mute, I want it to stay there. 

I'm not sure an "end of song marker" would result in less clicks to accomplish what you want. When rendering, if SONAR thinks the song is longer than you do, you can define the song length with 1 click + 1 drag in the timeline. With an end of song marker, I think best case would be if you could select it from a custom button on the Control Bar. So that would require 1 click on Control Bar + 1 click on timeline where you want end of song. They seem about equivalent in terms of effort.
 
The use case I see where it would allow for fewer clicks is if you were rendering multiple times during the course of doing a project, because once you had the end of project marker in place, you wouldn't have to think about it again unless you wanted to change the song end.

I agree wholeheartedly with Afrodrum. I would like to have a simple, one-click End of Song marker.

I truly appreciate all the effort it takes to come up with various workarounds. Workarounds are definitely preferable to having no solution at all, so many, many thanks to all those who put in their time and are so generous with sharing their discoveries and wisdom.

Wouldn't this be great, though: Whenever and for whatever reason, you decide that a certain spot should be the end of a song (at least, for now: you may wish to use an extended version at a later time), you click "End of Song". Done! Now, on to whatever you feel like doing next! What a nice feeling😀

I repeat, the workarounds are invaluable and much appreciated. It's just that, sometimes, I feel like my memory is packed with everything I have going on at my job and my life feels very stressful. I don't like to admit it, but I don't want to have to memorize any more workarounds. For those who work all day or very frequently with Sonar, I guess that isn't so much of a strain.

In my situation, though, the clearer and more obvious, the better. I guess, in sum, I'm calling myself a moron 😜

LJ

skinnybones lampshade
Wouldn't this be great, though: Whenever and for whatever reason, you decide that a certain spot should be the end of a song (at least, for now: you may wish to use an extended version at a later time), you click "End of Song". Done! Now, on to whatever you feel like doing next! What a nice feeling

What I want to wrap my around is why this would be so useful. The only time I can think of where I need to specify an end of song is when rendering, and as pointed out previously, the clickstream would be about the same as click+drag.
 
I think some people would like it to force an end to recording, but I would most definitely not want that. I would prefer that recording be able to keep going past the end because you might end up playing past the end and want to keep what you play.
 
The purpose of starting this thread, which seems to have been lost in the mists of time , was to find out what causes the existing "end of project marker" (i.e., the last event) to appear at someplace unanticipated. If it always appeared where expected, then having a separate end of project marker would be essentially a workaround. IOW, a correctly functioning automatic placement seems like a better way to do things than having to specify the end manually. My goal is finding out how to make the automatic placement work every time.