When you apply an effect, when does Audacity write the UNDO? I think it may be a terrific chance that the cache service dropped off-line or is being interfered with.
Everybody is on Win10? Everybody’s using the same virus software?
Koz
Has that wav file gone over 4GBytes? Try opening it in windows media player or the new windows player. If it is truncated to a very short run length the header may be corrupted through being oversize. Files like this can usually be recovered by using import raw in Audacity but they need to be saved to some other format such as RIFF ( rf64).
So did a full uninstall and re-install of audacity. That hasn’t worked. I put the files on another pc (running Windows 7 iirc, it was my brother in-laws) - and the problem went away. This weekend I will try a full Windows 10 re-install and see if that fixes it… So not looking forward to that being my weekend…
So did a full uninstall and re-install of audacity.
In Windows, there is a check to reset all preferences and settings. Did you check that box? If you didn’t Audacity will have hung on to all your old settings.
Koz
That’s a bit drastic! Have you tried running sfc /scannow at an admin command prompt? That would check the integrity of all the windows system files and usually fixes any bad ones.
Not sure if this has been answered, but this just happened to me out of the blue. Same message if I tried saving, copying or applying an effect to the whole file. While trying to copy the track piece by piece to a new track, I failed a section that had become corrupted. I copied and pasted everything I could to a new track/file and re-recording the missing piece.
Not sure where to post this but I’m having a similar problem. For the past six months, I record a sermon at church. I exit Audacity and always say Yes to save again or save. I then go to Windows Explorer and send the file to a thumb drive.
I take the drive home and insert it on my home computer (both machines are running the latest version of Audacity (3.3.3).
I bring up the sermon, edit it, and save a file_EDITED version of the edits, keeping the original audacity file intact.
I then go to File / Export / Export as MP3. This always works fine.
I had two sermons from this past sunday. One worked fine as norma. The second file came up with an error, “Audacity failed to read from a file in D:.”
I’ve tried several things including making a copy of the aup file and renaming it “test.aup” as well as making sure there were no characters in the filename that were not allowed.
Pretty frustrating. I have not yet gone back to the original computer and see if I could do something with it there. Since one of the files worked and the other didn’t, and I’ve been doing this for at least two sermons a week for six months, it’s weird that it’s anything else besides something with Audacity.
The laptop at church is running the latest patches to Windows 10 and I’m running the latest Windows patches to Windows 11 at home.
Given this has worked for six months and one of the two files worked from Sunday, it is just pretty weird. The AUP file plays the audio fine. No errors or problems.
Thank you.
Here is the debug code:
{
“timestamp”: 1693231974,
“event_id”: “d63b5df1459cc443aa2992b2e57d6fa3”,
“platform”: “native”,
“release”: “audacity@3.3.3”,
“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::GetBlob::step”
}
}
}
]
}
}