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
"Audacity failed to read file on drive c:"
Forum rules
This forum is for Audacity on Windows.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
Please state which version of Windows you are using,
and the exact three-section version number of Audacity from "Help menu > About Audacity".
Audacity 1.2.x and 1.3.x are obsolete and no longer supported. If you still have those versions, please upgrade at https://www.audacityteam.org/download/.
The old forums for those versions are now closed, but you can still read the archives of the 1.2.x and 1.3.x forums.
-
kozikowski
- Forum Staff
- Posts: 69357
- Joined: Thu Aug 02, 2007 5:57 pm
- Operating System: macOS 10.13 High Sierra
-
roadsterUK
- Posts: 187
- Joined: Sat Apr 15, 2017 8:00 pm
- Operating System: Windows 10
Re: "Audacity failed to read file on drive c:"
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).bobwasab wrote:BUMP
i am dealing with this right now as well. pretty much all the same stuff -- i can't apply effects or export audio, though about a week ago i was able to. saved to my C: on windows 10, plenty o' space, i can play the audio but exporting and effecting don't work, etc. etc. etc. these are the two messages i get, first one is when i try to export, second is when i try to add effects:
Re: "Audacity failed to read file on drive c:"
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....
-
kozikowski
- Forum Staff
- Posts: 69357
- Joined: Thu Aug 02, 2007 5:57 pm
- Operating System: macOS 10.13 High Sierra
Re: "Audacity failed to read file on drive c:"
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.So did a full uninstall and re-install of audacity.
Koz
-
roadsterUK
- Posts: 187
- Joined: Sat Apr 15, 2017 8:00 pm
- Operating System: Windows 10
Re: "Audacity failed to read file on drive c:"
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.Zer01337 wrote: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....
Re: "Audacity failed to read file on drive c:"
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.