Repair .aup (mac os, audacity 3.7.8)

Audacity 3 Help Forum macOS
1

audacity often cannot reopen a .aup project-file, showing the following errorcode:

{
“timestamp”: 1787230959,
“event_id”: “39b2b0a86e4c443c8dd35b55fccaca2b”,
“platform”: “native”,
“release”: “audacity@3.7.8”,
“contexts”: {
“os”: {
“type”: “os”,
“name”: “Macintosh”,
“version”: “26.6.2”
}
},
“exception”: {
“values”: [
{
“type”: “File_Error”,
“value”: “Audacity failed to read from a file in /.”,
“mechanism”: {
“type”: “runtime_error”,
“handled”: false,
“data”: {
“sqlite3.rc”: “101”,
“sqlite3.context”: “SqliteSampleBlock::Load::step”
}

any ideas how to handle that - how to repair the file?

2

Do you really mean an aup file (actually a folder) or an aup3 file? It’s important. If you are quite tech-savvy, you can try the audacity project tools to repair your project.

3

its .aup3-files

4

If you would like to share it and let me have a look, I could do with knowing how large the project file is.

5

that would be great
its about 1gb

I’m uploading it to my dropbox (will take an hour) and post the link

6

I’ll look out for that.

7
8

OK, I did manage to salvage something using a combination of tools. I can’t guarantee it is complete but I hope it helps. The download link is here: Link to recovered project
If your recordings tend to be like this ie single tracks, save them as WAV or FLAC so that you always have something to go back to and edit if the Audacity project gets corrupted.
Please post to say if you can use the project as-is.

9

Thanks Mark !!

you’ve given me back a few nice minutes of improvisation!

The file gives the impression that you didn’t just press a button in some program, but that you put a lot of work into it.

Is that right?

It still makes me quite uncertain, as I haven’t yet understood exactly what causes a corrupted file, or how I can avoid such a situation in the future.

Do you know if corrupted files are a common, general problem with Audacity?

1 Like
10

That’s good to know.

Somewhere between those two extremes but definitely closer to the button-pressing end of the spectrum. :grin:

I can understand the uncertainty. The developers will have the best idea of the causes of the corruption; I don’t. I have looked at quite a few broken ones and recovered maybe 3/4 of them. It’s not nice having to tell the minority that their work is lost. I suspect corruptions account for a tiny fraction of the millions of projects people have on the go but they do happen sometimes. My advice about saving to WAV or FLAC still stands. My plan B is to have Ocenaudio installed as well as Audacity. It doesn’t use project files.
If you think you might gravitate towards multi-track recording, change to a full DAW (digital audio workstation) program.