I’ve used audacity for years now and never had that problem before.
When I try to open my project (.aup), it is said : “project.aup” is an Audacity Project file. Use “File > Open” command to open Audacity project.
When I use the File-Open command, I get the same message.
So I can’t open my project, even if it seems going all well (the _data file is uncorrupted and named the same ; I can try to import one of the .au file and it works, but it would take days to try to put all the .au fils together).
I’m probably going to get fired if I can’t open this project.
Which version of Audacity did you use to save that project? And which version do you have now? See Help > About Audacity… .
The main (known) reason this happens is if you shut down the computer before the project has finished saving. The AUP file is saved last. When you save, keep the mouse still and look for the “Saved project” confirmation bottom left in the Status Bar.
I am using the 2.1.2 version, I haven’t done any (known) update since I recorded that project.
I have no backup copy, because I just recorded it, saved it, and the day after, tried to play it, and it didn’t run.
I guess Gale’s explanation makes sense. It could be possible (not likely but actually possible) that I’ve just closed my laptop before the recording was totally ended, at the end of the meeting. Which would explain why I can have the data but not the the aup. file…
I am using the manual recovering procedure (renaming every au. file so that they are in the chronological order, then create an aup. file from that) and I get a weird result, with blanks time to time, but at least 60-65 % of the sound, thank God.
Believe me, understanding what happened makes it less painful… Thanks a lot.
If you have any idea how I could have a better recovery of the file, don’t hesitate.
By first creating a WAV file using the “1.2 Recovery Utility” I assume?
Did you recover the AU files from the _data folder of the project or from the temporary folder (by default, C:\Users<your user name>\AppData\Local\Audacity\SessionData)? In your case you should recover from the _data folder.
However, when you first save a project, the AU block files get moved from Audacity’s temporary folder to the _data folder for the project being saved. If you did shut the computer down while that file transfer was still going on, then the files that did not get transferred might conceivably exist in the _data folder as zero bytes files, but for sure, some AU files would get left behind in the temp folder.
It is possible then that some of the blanks in the recovered audio might still exist as valid AU files in the temp folder, inside a folder called “project” followed by a number. If so it would be possible to add those files to the _data folder, rename and recover again, then you might have the complete audio but with inserted silences which you could then delete.
I open that new .aup file that is downloaded and it works, with 4 or 5 blank seconds every 12 seconds
PS: I also have to say that when I open the .aup file I’ve downloaded, Audacity sends me a dozen of error messages, saying that I should’t do that, that there are some “orphan pieces” that belong to somewhere else, that some of the pieces are unreadable (the blanks maybe?), etc. I say continue-continue-continue and I can finally play it, with the problems I’ve mentioned… I have the same message of unreadability when I import manually .au pieces: some of them are imported correctly, and I have a 4 seconds long recording, and some of them are not importable.
It is a seducing theory. I thought of this temp folder surfing on the internet, but it is absolutely… EMPTY! There isn’t anything in it, so all the very tempting procedure you’re talking about is in vain.
There is a script https://forum.audacityteam.org/t/alternative-recovery-tool/30964/6 that works by recreating the AUP file from the data, without renaming files. As with the other methods, it is only designed to work for unedited recordings. I believe that script works properly but we don’t usually mention it because it requires installing python and using the command-line, which most Windows users are not prepared to do.