Em, after moving my "portable" 2.3.0 instance to the fresh Windows 10 reinstall (to 1809 LTSC) the -old1.wav -old2.wav copies started to appear when overwriting export WAVs.
I'm not sure what caused this behavior, but I'm happy with it nethertheless.
Search found 3 matches
- Sun Apr 14, 2019 4:10 pm
- Forum: Adding Features to Audacity
- Topic: .bak rename overwritten export file
- Replies: 8
- Views: 772
- Mon Oct 22, 2018 12:39 pm
- Forum: Adding Features to Audacity
- Topic: .bak rename overwritten export file
- Replies: 8
- Views: 772
Re: .bak rename overwritten export file
Well, today I've just lost more than two hours of late night work because I was exhausted and accidentally overwritten older .wav over the hard night's work. It's completely vanished. The Undelete doesn't work too well in this case because the filename is the same. Can't express how frustrated I am ...
- Fri Aug 24, 2018 1:56 pm
- Forum: Adding Features to Audacity
- Topic: .bak rename overwritten export file
- Replies: 8
- Views: 772
.bak rename overwritten export file
It would be nice to have an option to make Audacity make a copy (.bak) when overwriting an already existing file through Export/Export as function. I.e., if you export as WAV to c:\Music\Untitled.wav and Untitled.wav already exists in c:\Music\ , then Audacity first renames existing Untitled.wav to ...