A trick that might be worth trying is re-wrapping all the files using ffmpeg, in windows I use a batch file something like this:
for /r %%A IN (*.wav) DO ffmpeg -i "%%A" -y -c copy "%%A_FIX.wav"
When run this will recursively search a folder for wav files then wewrap them leaving the audio data unmodified. I use a similar script to create mp3 copies etc and it can be very useful.
FFmpeg would have to be listed in your windows PATH variabales for this script to work.
I can provide a link to the batch file and some advice if that would help.
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
From: Association for Recorded Sound Discussion List [mailto:[log in to unmask]] On Behalf Of Richard L. Hess
Sent: 28 January 2019 19:00
To: [log in to unmask]
Subject: Re: [ARSCLIST] corrupted WAV files
While drive makers don't fail a drive for one reallocated sector, all my good drives have zero reallocated sectors. I am very suspect of a drive with any reallocated sector counts. I've had a few stay very low (1-2), but by and large once they start happening, they grow.
On a more positive note, I've had very few drives in the last five years get reallocated sector count hits.
On 2019-01-28 1:52 p.m., John Schroth wrote:
> Hi Richard:
> As far as I can tell, source files that became corrupt were still in
> the Wavelab cue for batch rendering to CD resolution files when my
> system locked up. I have no explanation as to what happened. I'm
> beginning to wonder if the drive that the master files sit on, is
> starting to become suss. I'll run some tests when I have the time to check it.
> Best Regards,
> John Schroth
Richard L. Hess email: [log in to unmask]
Aurora, Ontario, Canada 647 479 2800
Quality tape transfers -- even from hard-to-play tapes.
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.