@ Afrodrum    I haven't really thought about it that way, guess it's because of workflow differences. What I was really talking about though was the problem of data being hung way out after the end of a song and not really sure how it got there. I can see where the end of song marker could be handy in your scenario though.

Anderton
 
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 have to admit it works. It is less convenient than EOS marker, but works.

Guitarpima

Anderton

Guitarpima
I don't think so. I think Sonar is just broken. I've had projects with no automation and still have the problem. 

See post #3. I already addressed this, but I can understand how signal sometimes get buried by noise.

I guess you would know. Have a nice day!

 
Not quite sure how to take that...but if I wasn't clear, what I meant was that when a thread goes off in a lot of different directions ("noise"), the points that relate to the original premise ("signal") can get lost.

Anderton

Guitarpima

Anderton

Guitarpima
I don't think so. I think Sonar is just broken. I've had projects with no automation and still have the problem. 

See post #3. I already addressed this, but I can understand how signal sometimes get buried by noise.

I guess you would know. Have a nice day!
 
Not quite sure how to take that...but if I wasn't clear, what I meant was that when a thread goes off in a lot of different directions ("noise"), the points that relate to the original premise ("signal") can get lost.

I thought you were being otherwise. My mistake. I was just sharing my experience. I haven't gone the route of fully uninstalling and reinstalling. There could be something there but it's not such a huge deal to go through all that trouble.

AHA! Possibly another clue...
 
Referring back to post #3, I confirmed this is how SONAR acts. However if you do the experiment in post #3, insert several tracks, record-enable all of them, and start recording, only the highest-numbered track will place nodes as described. Nodes will not be placed on the other ones.
 
I'm not sure of the significance, but like I said...possibly another clue.
 
 

I tested as you described with 3 audio and 1 midi track. Sonar wrote the nodes for all four tracks for me at the record stop point. I only checked the volume automation, forgot to check pan.

teego
I tested as you described with 3 audio and 1 midi track. Sonar wrote the nodes for all four tracks for me at the record stop point. I only checked the volume automation, forgot to check pan.

I recorded only audio tracks. Will try adding MIDI to the mix... 

I'm looking at my current project.  In several tracks, exclusively midi, there are "clip" outlines extending way out .   I know if I use "bounce to clip" they will all disappear.   In each, there do seem to be automation envelopes that I didn't write, don't want, don't use, don't like, and wish would disappear.    Should CW decide to fix this problem, maybe that would be a good place to look.     As good general rule, CW:  DO NO HARM.    Any automatic thing, unasked for by the user, is probably going to cause problems for many users. 

Anderton

Kalle Rantaaho
Sounds like a good candidate for one cause of the problem.
I have encountered the never-ending-song phenomenon in projects that have no automation.

As far as I can tell SONAR is always recording automation, even if it's just a straight line - I believe that's how it knows where to restore fader values when you open a project. For example, if you set a fader to -6 at the start of a track, SONAR will write an automation value of -6. You need to enable the Write automation only if you want to deviate from this static value. Try this:
 
1. Create a new project.
2. Insert an audio track. 
3. Start recording.
4. Stop recording.
5. Unfold the automation lanes, and you'll see automation has been written for the current fader and pan positions, and an automation node has been inserted where you stopped recording.

Craig, I'm not seeing this.
 
I tried the above and at step 5, there is no automation for pan.
Also, if you simply insert an audio track without recording anything, then unfold the automation lanes, a volume envelope is created automatically.

I think the envelopes are actually created when you open the automation lane for the control. I say this because if you do the recording and then look at edit/ undo you have the option to undo recording,no mention off automation at that time. Then open an envelope lane and look at edit/undo and you will see the option to undo add automation lane at that time.
 
 Craig ,I tried it with all audio and it produced nodes at all tracks at the record stop point.