Hey brains trust,
I've got a file issue I haven't come across before and after a quick search I couldn't find any similar problem. Nor would I really know how to search it...
Back in 2022 I recorded a 'The Hold Steady' residency in Melbourne, Australia. First and third night recordings came out fine no dramas. Second night had the dreaded 0-byte error. I didn't know how to fix at the time so I just let it be. Living on my SD card taking up 4gb of a 12gb card. Long story short, in the last few weeks I've tracked those 2 shows as well as a residency they did last year in Melbourne and I looked into recovering the file. Used the chkdsk method and recovered it in a hidden file. Booyah achieved! Used VLC to get it back to a .wav that SoundForge could recognise. Was happy as Larry because they played a bunch of unique songs at this show of all the 8 times I've seen them. Strangely though when I opened the file in my editing program of choice the 2 hour set was almost 4 hours long. Looking closer the first hour and 45 minutes are fine. But for some reason in the final track which would normally run 10 minutes or so is 90 minutes long. Can understand why the file errored...
Now, the error starts about 4 mins and the best I can describe it is that after the 4 minute mark the file plays 2 seconds of audio, then skips back 1.9 seconds. Then plays 2 seconds of audio, then skips back 1.9 seconds again and so on and so on. So very very slowly the track is advancing but it is continuously jumping back in time as it does it. I've included a short youtube link here (
https://youtu.be/094UUWrPxAc) so you get the idea. The error starts at around the 15 second point in the video.
Has anyone encountered an error like this before and have any idea of how to fix it? I know that I could manually go through each 'skip' and delete but I feel that would take much more time than I have at present time. I've tried to attatch an image of the small snippet on youtube as well so you can visually see it as well.
Here's a link to the .wav of the affected song if anyone wants a closer look. It is 1.5gb in size...
https://www.dropbox.com/scl/fi/z8yt8tsdqeyauy2qxpa34/FILE0010.wav?rlkey=8d21sszh42ojfb5vljxzpjcug&dl=0Thanks in advance. I look forward to seeing what you guys can deduce from this one.