Bad surprise yesterday: a file on which I worked the two last weeks crashed suddenly.
It is now impossible to re-open. I make just an attempt here before starting from zero…
Thanks by advance for your help!
There is the error code:
{
“timestamp”: 1701105373,
“event_id”: “db168263cfcf1e418b5bc7e54b58e357”,
“platform”: “native”,
“release”: “audacity@3.4.2”,
“contexts”: {
“os”: {
“type”: “os”,
“name”: “Windows”,
“version”: “10.0.19045”
}
},
“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”
}
}
}
]
}
}
I can’t give a definitive interpretation of the errors, but at first glance, Audacity lost track of the drive. Are you using external, network, internet, or cloud drives? The manufacturers go to great lengths to make their cloud drives look just like a local drive, but they’re very much not.
Koz
If you do have an extended project, it’s a terrific idea to do a backup periodically—even if you’re not done with the show. It’s a common mistake to File > Save Project as you go. Don’t do that. That just saves one file over and over.
Instead, File > Save Project > Save Project As… with a new filename.
CoolShow-20231125.aup3
CoolShow-20231126.aup3
CoolShow-20231127.aup3
Do it, for example, once a day with the date burned into the name. Or more often.
Please know that only upper case, lower case, numbers, underscore,
and dash may be safely used in filenames. I don’t use spaces, either (above).
Once you make those safety files, you can move them to wherever you want. Just don’t let Audacity see you do it.
Koz
Thank you for answering. The files are just on a hard ware storage … You think that the problem came from that?
This topic was automatically closed after 30 days. New replies are no longer allowed.