recorded a song yesterday , and saved it as a .aup, as you do. But when I went back to open it today, it kept saying the file “is an Audacity Project file. Use the ‘File > Open’ command to open Audacity Projects” with the window title of “Error Importing”. I did go to “file” and then “open” to access the file, but the same error message came up.
It is version 2.1.2 on windows 10. It opened and closed fine all last night and I have not moved or changed the files. I did switch my pc off last night, but the other song I recorded still opens fine and is the same type of file saved at the same time.
Bit annoying since took me 4 hours to record yesterday, is there anything I can do or is the file just corrupt?
Manual Recovery (at the bottom of that page) only works with a mono, not stereo recording. So the performance may be gone. It’s not a bad idea to Export a WAV (Microsoft), 16-bit of important work in addition to the Project. That’s a standard sound file that should open up anywhere.
I agree it’s a concern but is it really only Windows 10? I think we will have to track this as a “bug”, albeit not reproducible. The number of reports of empty saved AUP files went up as soon as we made the AUTOSAVE file a binary file rather than a human-readable XML file. It is a good bet there is a correlation.
On the other hand, the problems we used to have with the error where the AUTOSAVE file was not writable have disappeared completely as far as I know.
We went through this in a Private Message, Koz, if you recall. There are two pages.
if you are suggesting 2.1.4 will have a single file project format.
That’s what my ball said.
Of course, it’s not necessarily the final arbiter of technical prognostication, and further, it’s not even my ball. That’s my grandfather’s ball. I can’t find mine. It may be in a box in the garage [shudder]. I’m using the filial links extension and it seems to work OK.
But I do wish I could find mine. There’s just something about using a ball that could very well be older than I am. Creepy.