Anderton
The only difference is that the transport doesn't stop playback automatically after recording, but so what?

IMAGINE YOU ARE RECORDING YOURSELF!!! VERY NICE TO HAVE THE TRANSPORT STOP AUTOMATICALLY, RIGHT!?
 
So yes, a big deal for me especially since I swear we used to have that feature and I happily used it exactly as I am describing.

dougalex

Anderton
The only difference is that the transport doesn't stop playback automatically after recording, but so what?

IMAGINE YOU ARE RECORDING YOURSELF!!! VERY NICE TO HAVE THE TRANSPORT STOP AUTOMATICALLY, RIGHT!?
 

Honestly, not really. I see it as six of one, half a dozen of the other. The way it is now, I place the cursor where I want to start hearing the music, hit R, hit the space bar when I'm done, and I'm back to where I started. The recording stops automatically anyway, which what I care about. I wouldn't want to hassle with drawing a second region in addition to the punch one, enable some function that would tell the loop not to loop instead of the default behavior, then figure out what to do after it had stopped automatically (unless part of your feature request is to have it stop and rewind automatically back to where you placed the now time originally).
 
I just don't find it a big hassle to hit R to start punch recording and hit the space bar to stop, but if you were going to do the same part over and over and over and over and over again I can see where it would be worth the setup time to define the secondary region and initiate the "stop here" function. But hey, put in a feature request and see if it gets traction.
 
I think a better feature request might be the option to create a "song end" marker. You could put this where you wanted your adventures in punching to end, but also, it would stop all the forum posts about "hey, the end of the song is longer than the end of the song" - I wouldn't have to explain the part about trimming clips and deleting the region where automation nodes might be left over. So it would solve two problems instead of one.
 

You aren't crazy, op. Others have wanted this. It might be a feature some would use.

I'm with others that I don't think I would care, but it is sufficient that you do care.

Submit a feature request.

Anderton,
Interesting that I found an article you wrote many years ago mentioning "Sonar defaults to continuous looping"
http://www.soundonsound.com/sos/may02/articles/sonarnotes0502.asp
 
See sonar had more robust looping many years ago:

 
 
Was still a feature as least as late as Sonar 7, did not check 8.5 yet. Must have got ditched in X1.
 
Again, I was very happy years ago when was tracking myself. Now frustrated losing something I liked and so "Loop once and stop" was a actually an important work flow feature for me. Now, after returning to doing overdubs by myself I realized why I am frustrated...some years ago they took away a nice feature that I used all the time. 
 
 
edit: removed link to bonus images, message content unchanged - scook

The spam blocker intervened. I restored one of your attempts to post and fixed the image link.

EDIT: Cannot record using this method, only playback (DOH!)
 
There is a usable workaround. You just have an extra step to select all tracks (or tracks you want to hear).
 
Anderton was in on this thread from 2013 and ends with workaround suggested by OP:
http://forum.cakewalk.com/m/tm.aspx?m=2939791
 
1. select part of track which going to play
2. Press "shift"+"space" key
It starts to play and at the end point automatically stops.
 
(I have made a feature request "Bring back 'turn off continuous looping' feature")

dougalex
1. select part of track which going to play
2. Press "shift"+"space" key
It starts to play and at the end point automatically stops.

Which version of SONAR are you using? When I try the above with Platinum, as soon as I press shift+space bar, the selection turns into a loop. Hmmm... 

Yes, turns into loop that is supposed to play once and stop, cues up at beginning of loop for next start by user.
Does yours loop continuously?
I am using Platinum.
 
Regarding my original comment, as a previous comment above said, there are a number of people who want to this functionality back. Would not be as frustrating if I had not enjoyed the feature and had it taken away....I can't imagine why a useful feature that existed for almost 15 years would get eliminated.