New User Corrupt File


I am a brand new user. I have been using Audicity over the past week learning how it works and how to edit in it. We are starting a new podcast and recorded the first show last night. Today, while editing, the file became corrupt. I had a backup copy that also was corrupt. I learned my lesson and should have immediately saved a raw audio version and then create a working file, but I didn’t do that.

When I try to open the file in Audacity, it says, “Audacity failed to read from a file in D:” and gives the following problem details:

“timestamp”: 1687812980,
“event_id”: “ca07c38761126643a6ed47b2e38547aa”,
“platform”: “native”,
“release”: “audacity@3.3.2”,
“contexts”: {
“os”: {
“type”: “os”,
“name”: “Windows”,
“version”: “10.0.22621”
“exception”: {
“values”: [
“type”: “File_Error”,
“value”: “Audacity failed to read from a file in .”,
“mechanism”: {
“type”: “runtime_error”,
“handled”: false,
“data”: {
“sqlite3.rc”: “11”,
“sqlite3.context”: “SqliteSampleBlock::Load::step”

I have attempted the recover process using the AudRepair tools but I get the error “unable to open database file”

I am not sure what else to try. Any help would be greatly appreciated. I have preemptively uploaded the file to my google drive if anyone is able to help:

I don’t have the life-expectancy to download a 6.8Gb file
six-point-eight gigabytes
aup3 file-sizes are unfeasibly large:
6.8Gb is enough for >5 hours of 32-bit stereo 44.1kHz audio.

I can appreciate that. Sorry. Any help in pointing me in the right direction to recover it?

It’s the developers of Audacity who should be sorry:
they are releasing unreliable software onto an unsuspecting public. :disappointed:

Apparently Jademan has had some success …

From Trebor’s link: “If you see the message, “unable to open database file”, you have simply mistyped the file name or the .aup3 file name extension.”

I saw the instructions saying that I “simply mistyped the file name,” but I have tried mulitple times to ensure I did it all correctly. Maybe I’m missing something, but I typed it in exactly as listed.

Please post a screenshot showing the results of the “dir” command and all the following lines up to where you get the error.

This topic was automatically closed after 30 days. New replies are no longer allowed.