Audacity Forum

I just looked at a current AUTOSAVE file and it is definitely different than the ones that were recovered! There is a lot of stuff missing from the beginning of the AUTOSAVE files I want to recover.

jaja714 wrote:I have restored the .AUTOSAVE files into "C:UsersMeAppDataRoamingAudacityAutoSave" and all of the .AU files into the correct temp directory and then correct subdirs (ex; "C:UsersMeAppDataLocalTempaudacity_tempproject5718e00d0ae000a0s2.au") but, alas, Audacity comlpetely chokes on this.

Yes that's the correct directory for the AUTOSAVE file. Audacity won't look in its temporary directory for the AUTOSAVE file.

The bad news is that the AUTOSAVE files you posted are just nulls (zero data). There is no way to use those files. What version of Windows are you on? Do you have "previous versions" of files enabled?

Are these unedited recordings, or have you been applying effects and moving parts of the recording around? If the recordings are edited there is no practical way to figure out without the AUTOSAVE file what the correct order of the AU files is, and no way to figure what data belongs to the state of the project when it crashed.

As Steve said, unless Recuva kept the original timestamps of the AU files, even unedited recordings can't be recovered in the correct order.

Next time, please export each recording as WAV as soon as you hit the Stop button.

Gale

Gale Andrews wrote: The bad news is that the AUTOSAVE files you posted are just nulls (zero data).

Not quite, but there is a load of invalid data at the start of the file.
As Gale wrote, unfortunately the file is irretrievably corrupt.

How did both files get corrupted in exactly the same fashion?

jaja714 wrote:How did both files get corrupted in exactly the same fashion?

Unfortunately we still don't know what version of Audacity you are using, but in case you are using an obsolete version, the current version is 2.0.5: http://audacityteam.org/download/windows .

AUTOSAVE files are created every time you perform most editing operations.

What is supposed to happen as I understand it is that the AUTOSAVE file is first created with a TMP extension then if all goes well it is renamed with the AUTOSAVE extension.

I "think" the previous AUTOSAVE file gets deleted before even the new one is created, and it's rare for there to be AUTOSAVE files left behind. If the AUTOSAVE can't be written the TMP file for that write usually gets left behind and has to be deleted manually. It's quite common on Windows for TMP files to be left behind.

I suspect Recuva just found the two remaining AUTOSAVE's that could be (to some extent) recovered. Audacity would have deleted all the AUTOSAVE's, bypassing the Recycle Bin.


Gale

I shouldn't be too far out of date as I am running 2.0.3.

Why doesn't Audacity just use the recycle bin for all cases where possible? At least this wouldallow users who accidentally close a project without saving to recover without much effort at all.

jaja714 wrote:Why doesn't Audacity just use the recycle bin for all cases where possible?

When closing a project, there could be tens or even hundreds of GB of temporary data to be deleted. Although modern hard drives can be very large, not everyone has a lot of free disk space, (particularly with new solid state drives). If temporary files were not deleted, then batch processing a large number of large audio files could easily fill all available disk space and cause the computer to crash. On Windows, recovering from a completely full hard drive can be quite tricky (Windows may not be able to boot up). Also, if a user restored all of the deleted files from their recycle bin, that could put thousands of orphaned files into a previously undamaged project, causing the project _data folder to grow enormously in size and creating thousands of errors the next time the user attempts to open the project.

Now before I give up, is this timestamp thing worth investigating? I do seem to have valid timestamps for all of these .AU files. So, without a valid AUTOSAVE file, would it help if I chronologically renamed the AU files?

We had a long discussion before with a couple of people who closed projects without saving by mistake. The upshot was that Audacity would have to handle this itself if it was going to handle it at all, for example by having a setting that made Audacity always reopen with whatever work it closed last time (saved as a project or not).

I agree with Steve that using the Recycle Bin for deletions is not an option. Some projects could generate hundreds of AUTOSAVE files. If those were restored from the Recycle Bin, Audacity would be trying to "recover" hundreds of "projects" next time you launched it.

jaja714 wrote:Now before I give up, is this timestamp thing worth investigating? I do seem to have valid timestamps for all of these .AU files. So, without a valid AUTOSAVE file, would it help if I chronologically renamed the AU files?

As explained a couple of times now, that would only work if the project was an unedited recording *and* Recuva did not change the AU timestamps from what they originally were. And if it was a stereo recording you will need extra efforts to recover the channels in correct order for the length of the recording.

You didn't answer about your version of Windows. If you have Windows Vista or Windows 7 and you have "System Restore" or "Backup" enabled, then you may have a "previous version" of the AutoSave folder. Right-click the folder to find out.


Gale

I can safely say that we've concluded all efforts to recover this particular project as I was able to re-record everything this morning. It's not as nice as the original that was lost but it will do.

Just to fill in a few questions. I am running Windows 7 64-bit. Yes, I have System Restore enabled but it only runs once a day at 3 am. So, all of the work I did that day could never be in the backup since I accidentally closed the project later that same day.

I see what you mean about using RecycleBin but I've seen other applications also use RecycleBin to store hundreds of files as well. I mean, storing them in RecycleBin is not that much different than storing them in AudacityTemp. Further, Audacity would only be using RecycleBin in the rare case where someone chooses to close a project (strike 1) while also declining to save (strike 2). Perhaps Audacity could check RecycleBin each time it is opened (just like it checks AudacityTemp) and, if something fitting that criteria is found, prompt the user to recover. If the user says no ... this is essentially the third and final confirmation (strike 3, you're out) ... remove all such project matter from RecycleBin. Again, since we are only talking about the case where someone chooses to close a project while also declining to save, this logic would surely only be triggered once in a blue moon.

So, the changes to Audacity would be as follows:

[*]When closing, move temp files into RecycleBin only when user closes a project while declining to save.
[*]When opening, check RecycleBin as well as AudacityTemp

Please do not let the tragic loss of my precious recording be in vain!