First-timer here! Running Audacity 3.0.4 on Windows 10. I’ve been using Audacity for about a month now.
Long story short: I believe my AUP3 file is corrupted as I can’t open it. I’ve spent a couple hours searching through the forums for a solution and it seems complete recovery of this problem is rare. I saw in a few places where they opened the file and recovered some of the audio blocks. I’m hoping that there is just a few blocks of audio that are bad, and that I can recover the bulk of the file. Is this a process I can try on my own, via some software or something, or is it exclusively a developer capability?
Long story long: Today I recorded an interview for a podcast through Audacity, and immediately saved it as an Audacity project (I’ve since learned that the proper way is to save a WAV file immediately, and then to back up that WAV file on thirteen separate external drives to make sure it doesn’t go bad haha). After running it through a compressor, I tried noise reduction and it failed. I then tried restarting Audacity, but it wouldn’t let me open the file. Here’s the error log if it interests anyone:
Tried saving an instance of the file on my desktop, and it still wouldn’t open. I’m hoping that there is at least a little bit of audio I can recover from this. Other pieces of information: I do not see other files, such as an AUP3-WAL file. I saved it initially on an external drive, and then tried again on my desktop. I have full permissions on both drives.
Anyone have any ideas?
You have the wave copies, right? So you killed your current edit, not the opportunity to repair it later. The high voice, wide eyes, waving arms forum postings are from the people with no back up and the only copy of their work is in that crashed project with the error messages and no sound.
on thirteen separate external drives
There’s recommendations for that, too. Be able to point to two different places that have your WAV copies. Internal hard drive and external USB thumb drive counts as two. External hard drive is one. Cloud drive is one. Home network drive counts as one. Two folders on one drive does not count. Audacity doesn’t always get along with exotic or remote drives, so make your local export first and then copy it to other drives.
What’s wrong with more than two? You have to make the habit of doing it every time you shoot something. If you shoot two interviews, that’s 26 file exports.
I’m hoping that there is just a few blocks of audio that are bad, and that I can recover the bulk of the file.
That doesn’t have a really good track record. Picking up where you left off generally invites another crash and even more damage. You should produce protection backups as quickly as you can assuming something of value comes of the rescue.
I then tried restarting Audacity, but it wouldn’t let me open the file.
If you have a crash or other super evil event, there’s some rules about that, too. Misbehaving software can leave trash laying around on the machine. Shift+Shutdown Windows > Wait > Start. Don’t let anything automatically start.
Shift+Shutdown resets more Windows processes and helps clean up after a crash.
I don’t know we ever found out what’s causing Audacity to damage shows like this. There was one tiny event a while ago where someone was having constant troubles and made them all vanish by freeing up a bunch of hard drive space. If you have a Solid State Drive, that’s all you do. They shuffle things around internally and it’s best not to interfere with that. If you have a spinning metal drive, you’ll need to free up room and then optimize or defragment it.
Not as far as I’m aware, though there has been some dev talk considering options for dealing with corrupt projects.
Fundamentally the issue is that working with media is a lot more demanding on the system than most other kinds of computer work. Some media apps (such as Pro Tools) even go so far as producing hardware specifically for running the app. On the other hand, Audacity typically runs on general purpose consumer PCs, and sometimes unsuitable systems (eg cloud storage, low RAM, small / slow hard drives, lots of background services). As Audacity gains shiny new features there is a tendency for the system requirements to increase, and while the shiny new features work fine on the developers machines…
It was about an hour long stereo recording. I don’t know much about how this stuff works, but it looks like the left and right tracks were merged together, so I get overlapping blocks about 11 seconds long. Is there an easy way to remove every other audio block?
I guess a little bit deeper question is what exactly constitutes a block? If it is an exact length of time, or a specific file size, then perhaps I can write a simple python script or something to remove every other block.
A Macro (in the outside world, “Batch” file) is a text collection of all the things you were doing by hand anyway. One significant shortcoming of Macro/Batch is a complete inability to make decisions. There is no: “if this happened, then do that.” You start it, it goes to the end, and then stops. No decisions, no branches.
This is a fragment illustration for the Audiobook Mastering Macro.
Those text lines keep going off the page on the right. They’re basically instructions how to perform an effect.
But just to illustrate, that’s an automatic method to apply Filter Curve, Loudness Normalization, and Limiter. Three Audacity effects.
The first line is from good programming practices to label and identify your program. It’s a comment. Ideally, it would have a release number, date, and author name.
It was notable that the by-hand job of mastering before the Macro was well established and stable. So this is the Macro version of a good, existing process.
Do you have a good working process to rescue the first minute or so of your show? If you can’t write down what you’re doing now on a legal pad, then programming it in anything will be a nightmare.