Ah yes... there it is. Thanks.
 
As for whatever else is going on here... doesn't seem the type of thing for folks to get excited about. But waddoikno? I'm just a Beep.
 
It probably should documented though... if it isn't already but that's what the online version is for (can be updated easily). I did a google moogly search and nothing came up aside from some stuff about opening older projects which has nothign to do witht his new feature.
 
Anyhoo... got the manuals now. I'll give them a good home in my docs and tuts file for easy access.

I hear you Beep. This thread was not intended to upset anyone. It was for my own curiosity and me trying to understand a new feature fully. 

I haven't tested it and would certainly like things such as this to be documented but I'd imagine a simple test should confirm what it does (which I will likely do myself soon).
 
My undertanding is...
 
Save As (which was the only option until now) = Creates a new project file of the current project. This leaves the previous saved version intact/as is (unless you specifically open and edit it) and now any changes made to the new Save As will be applied as soon as you click Save.
 
Save Copy As (new option) = Takes a snapshot of the project as is and sets it aside. You continue working in the original project and any Saves will only apply to the project you are working on. The Save Copy As version remains untouched (obviously).
 
Simple enough but the implication is that in theory now you can start your project, let's call it Platinum 1 Main, and use that project all the way until you complete the project. As you go you use Save Copy As to create backups at crucial points (Drums Tracked, Guits Tracked, Mix 1, Final Mix, Etc). This way if you main project goes nipples up you go back to your last Save Copy As.
 
To do this with the old Save As you would have to create TWO Save As copies of the project. The first one to take the snapshot and the second one to continue working with... which eventually would need to be Saved As twice again at each stage. This takes up more disk space (not much but it all adds up) and if you are obsessive about creating backup points your project folder ends up HUGE.
 
If your main, ongoing project gets corrupted (Platinum 1 Main) you revert to you last Save Copy As project, do a Save As (or Save Copy As) of that version to "Platinum Main 2" and that is now your new main working copy until you finish the project or experience another corruption event.
 
I know you probably know that already but based on some recent threads I think some people are having a hard time seeing the uses for this. I will definitely be using it.
 
Cheers.

Save Copy As is not unique to Sonar. Many editor applications use this function.
Here is the documentation from another prg.
 
 
There should be three options (though not in all programs):
"Save" - This will save the document without asking for a new name or location. It will over-write the original.
"Save As" - This will prompt you to save the document using a dialog box. You will have the ability to change the file name and/or location. If you choose the same file name and location it will over-write the original. Your working document will be the one you just saved.
"Save A Copy" - This will prompt you to save a 'copy' using the same dialog box as 'save as'. You will have the ability to change the file name and/or location. If you choose the same file name and location it will over-write the original. If you changed the name or location of the document you will be working on the original document not the copy. This means that if you make additional changes and then hit save the original will be overwritten with the new changes, but the copy you saved earlier will be left at the state of the "Save A Copy".

Some proper answers are called for.
 
I read "Save Copy As" - save everything this project contains, audio, midi, mix scenes - the lot to a new location - and references inside to anything is changed to the new locations folders.
 
So that you can open this project as is - without interference with source project.
 
That is what I hope for - but don't care to guess my way....

Jatoth and Beepster that is what I was looking for. I can wrap my head around it now. Thank you both! 

Susan G

Bristol_Jonesey

John
I have a feeling that I maybe over thinking this. 

Probably.
 
It works exactly the same as it does in Excel, Word etc.
 
The current file which is loaded into memory will not be overwritten when you "save as". It creates a brand new version.
all these programs give you the opportunity to change the file location and lots of toher stuff as well before the save is written - file type & file name being the obvious ones.
 
You can also use "save as" to keep the same name but file it in a different location.

Hi Colin-
 
That's "Save As...", not the same thing. John's asking about "Save Copy As". There's now "Save," "Save As" and "Save Copy As." I asked about it here: http://forum.cakewalk.com/FindPost/3167737 and the question was answered; it's just not documented.


-Susan

Quack quack oops!!

lfm
Some proper answers are called for.
 
I read "Save Copy As" - save everything this project contains, audio, midi, mix scenes - the lot to a new location - and references inside to anything is changed to the new locations folders.
 
So that you can open this project as is - without interference with source project.
 
That is what I hope for - but don't care to guess my way....

Yes it is like that but the new location is not a requirement. Its basically a name change without changing the current projects name in memory. A save as with no corresponding project name update.
 
Heck, anyway I try to explain it it still seems inadequate.   

John
 
Yes it is like that but the new location is not a requirement. Its basically a name change without changing the current projects name in memory. A save as with no corresponding project name update.
 
Heck, anyway I try to explain it it still seems inadequate.   

Yup, I think you've got it.  No need for feelings of Plat knowledge inadequacy around these parts.  
 
Personally, it's one of my favorite new features.  My current project has versions A-Y saved as minor milestones along the way, all using the Save Copy As command so that the active project was always the working version.  So not once during any session did I have to reload that working version like I would have using the traditional Save As command. 
 

Thanks Steve. Lets hope so. LOL