Is there a way to recover a project file?

[mgustavo]

Hi! I've been working on a project with a few instrument tracks, but I forgot "Ripple Edit All" button enabled, deleted a bounced mix and changed to other mix scene. It took me some time to relate those actions, because all midi content had disappeared, and I had already saved the file!
In resume, as I lost my work, is there a way to recover this project file ?
Thanks in advance!

Edited November 7 by mgustavo

[Bristol_Jonesey]

Restore from your last backup?

[Base 57]

If you have File Versioning enabled (on by default), you can click on File-Revert and see if there is a version that pre-dates the mistake.

[mgustavo]

Bristol_Jonesey, yes, I thought it could be like when using system restore point in Windows! I don't know if it would work!

Base 57, thanks, but I didn't enable this feature, maybe it could be a good practice!

I normally save a backup file but this time I had just forgot!
Thanks for the replies! 

Edited November 7 by mgustavo

[msmcleod]

There's no way to recover the project itself, but in the project Audio folder you should see previous versions of your wav files.  The date/time stamp for the files  should give you an indication as to what files were used just prior to your mistake

It's not an easy task, but you could try:

1. Copying the relevant project wav files to a different folder
2. Dragging each one into a new audio track
3. Solo each track and try to identify the sections you wish to recover

[mgustavo]

msmcleod, thanks for the input! That's a good workaround, I'll give give it a try!

[Amberwolf]

Other than versioning, another way that I use for *every* program that I save files from, is to

NEVER EVER

SAVE

But instead

ALWAYS  USE

SAVE AS

I re-bound the key in SONAR of CTRL-S to SaveAs, and used the menu editor to remove Save from the menu, and turned off the Standard toolbar with the Save icon in it since it can't be altered to SaveAs.   So there is literally no way to just save a file over itself without the chance to rename it.  

Then I use a file name that is the date, and a six digit number representing the project I'm working on that day, and a six digit number for the file version (and often a letter or set of letters representing significant changes to the project).   

So it might end up like this for the first project of the day

110124 000001 000038n  ProjectNameHere.cwp

110124 000002 000027A ProjectNameHere.cwp

for teh second, etc.

Doesn't matter what actual name you use, as long as you are consistent so you know what they mean.

 

The main point is to never ever save, and only use SaveAs, so that:

---you never accidentally lose data from saving over something

--you have multiple versions of the project so you can go back to any point you save-as'd at,   even if one file is corrupted or lost.  

 

 

Edited November 8 by Amberwolf

[Promidi]

On 11/8/2024 at 6:30 AM, mgustavo said:

Base 57, thanks, but I didn't enable this feature, maybe it could be a good practice!

Definitely enable file versioning.  That has saved my derriere on many occasions.