Imagine this. I had sometimes saved as to a different  hard drive as a backup. After which if I wanted to save again to my original "work" hard drive I would have had to saved as back to it.
 
Though I've not yet tried it, I think if I saved copy as in that scenario, I could just continue working and save as I saw fit, and it would be saving the original project with new edits to the original work drive...   I like the thought of that.

Paul P

FastBikerBoy
Nothing has changed. If I "Save as'd" in earlier versions I was in the new project. That's the same behaviour now for that command, "Save copy as.." has added to the save possibilities by leaving you working in the current project having just saved a new one.

I don't get it.  Before writing the above, I first retried it out to make sure.  On my X3eP, and I'm pretty sure my previous X2aP, if I Save As, I remain in the original project - while a copy with the new name is indeed created in the background.
 
Either that, or the window title doesn't get updated, but that would be problematic as you wouldn't know where you were.
 

Hi Paul-
 
I can't repro that. I just tried "Save As..." with X3e Producer and the window title changed to reflect the new project name.
 
@All-
 
Thanks for all the replies. I like the new "Save Copy As..." feature. I've been working in a couple other DAWs lately that implement a "Save New Version" and auto-append a number to the file name (leaving you in the new version,) which I like as well.
 
-Susan

Sixfinger
Imagine this. I had sometimes saved as to a different  hard drive as a backup. After which if I wanted to save again to my original "work" hard drive I would have had to saved as back to it.
 
Though I've not yet tried it, I think if I saved copy as in that scenario, I could just continue working and save as I saw fit, and it would be saving the original project with new edits to the original work drive...   I like the thought of that.

Hi Sixfinger-
 
I just tried what you suggested, and it does work exactly as you describe (save copy as to a different drive; pick up where you left off in the original.) Nice!
 
-Susan

Paul P

FastBikerBoy
Nothing has changed. If I "Save as'd" in earlier versions I was in the new project. That's the same behaviour now for that command, "Save copy as.." has added to the save possibilities by leaving you working in the current project having just saved a new one.

I don't get it.  Before writing the above, I first retried it out to make sure.  On my X3eP, and I'm pretty sure my previous X2aP, if I Save As, I remain in the original project - while a copy with the new name is indeed created in the background.
 
Either that, or the window title doesn't get updated, but that would be problematic as you wouldn't know where you were.
 

Definitely something going awry there then. I've personally never seen that in any version I've ever used starting at V2.
 
It's part of my normal workflow, saving landmarks at end of tracking, editing, changes with audiosnap etc. etc. not to mention a load of mixes (which has now been improved with the mix scenes feature) so I would definitely have noticed had that ever happened.
 
I like to keep just one "current" project, all the landmarks are there should I wish to revert to any of those as a starting point. Previously I had to reload that project after every "Save As...", now I can "Save Copy As..." and carry on working.
 
I find it's usually the "little" things that make the big differences. Loving this one. 

FastBikerBoy

Paul P

FastBikerBoy
Nothing has changed. If I "Save as'd" in earlier versions I was in the new project. That's the same behaviour now for that command, "Save copy as.." has added to the save possibilities by leaving you working in the current project having just saved a new one.

I don't get it.  Before writing the above, I first retried it out to make sure.  On my X3eP, and I'm pretty sure my previous X2aP, if I Save As, I remain in the original project - while a copy with the new name is indeed created in the background.
 
Either that, or the window title doesn't get updated, but that would be problematic as you wouldn't know where you were.
 

Definitely something going awry there then. I've personally never seen that in any version I've ever used starting at V2.
 
It's part of my normal workflow, saving landmarks at end of tracking, editing, changes with audiosnap etc. etc. not to mention a load of mixes (which has now been improved with the mix scenes feature) so I would definitely have noticed had that ever happened.
 
I like to keep just one "current" project, all the landmarks are there should I wish to revert to any of those as a starting point. Previously I had to reload that project after every "Save As...", now I can "Save Copy As..." and carry on working.
 
I find it's usually the "little" things that make the big differences. Loving this one. 

Personally I like to "save as" with a new revision number as the project is progressing. One advantage I see for the "Save Copy As" feature is to make a backup copy on another drive w/o relying upon whenever my backup software is going to kick in.
 
Walt

I just tested the save as and it definitely changes the name of the loaded project in both X3e Pro and Platinum.
 
Unless I am misunderstanding this this is the way I have always known Sonar to act.

 
Thanks to all for the confirmation that things are and were as they should be, at least on your systems.
 
I'll be looking further into the matter.  Don't know and can't imagine why I'm getting a different result.
 

One problem I can not find any reference to save copy as in the help file. 
 

John
One problem I can not find any reference to save copy as in the help file. 
 

I don't think it is, hence the OP. One of the joys (??) of scripting videos is fathoming out the features. 

FastBikerBoy

John
One problem I can not find any reference to save copy as in the help file. 
 

I don't think it is, hence the OP. One of the joys (??) of scripting videos is fathoming out the features. 

I think CW just doesn't know how to describe it!