Hello, I’m having big trouble with a working session, coming from external drives, which I think contains corrupt WAV files.
When copying the folder to my system and then working on it (in Pro Tools), it works for a while and then suddenly it doesn’t open anymore, and I get two error messages:
- Could not complete your request because Assertion in “..\ ..\ FF\ Audio\ FF_AudioFile.cpp”, line 1092.
- An error regarding the memory locations list ?!?!?
Also, sometimes I got a PARSING error on some clips and then they just play noise in playback. In stereo files this can happen on 1 channel, while the other is empty.
So I tried opening the session on its original external drive and SAVE COPY IN, but at one point Pro Tools quits unexpectedly, every time.
So I think there are some corrupt files, but the project being quite big, I can’t go through every single one of them.
Question: Is there a way/software to FIND corrupt WAV files? A batch analyzer of wav files? Or a workaround to find corrupt ones?
I found this software which can fix some issues in WAV files regarding Pro Tools, but the first problem is to find them in a huge session.
Thank you Doug and Shaun!
Actually I just stumbled upon an audio files batch processing software called MYRIAD. I’m using the demo and added the Audio Files folder: TA DA! It found some corrupt files, specifically with two different problems: “data chunk not found” and “loading split file failed because the frame count differ”.
I’m going to try and remove them from the original session and the SAVE COPY IN again.
This software looks interesting, it has lots of batch processing features for audio files, it could be useful for post people. The fun part is that it naturally finds corrupt files on import but it doesn’t seem to have handling/processing capabilities on them. I’ll need to read the manual but, if not present, it would be great to add features to move/remove corrupt files from folders.
It can be helpful to create a new blank session file and import the tracks into it. Try using that session. If the problem has gone away, you’re good to go. If the problem persists, make a new empty session and import half the tracks into it. See if the problem persists. If it does, your corrupted file is in the tracks you have imported. Keep importing fewer tracks into an empty session until you have found the culprit track. The corrupt clip is in that track.
This can be very time consuming. Also, the corrupt clip could be in multiple tracks, or indeed, the corruption may not be in a clip at all, but rather somewhere else in a track.
One possible source of an error is an illegal character in an audio file path name.
You could also try copying the media files by doing the import tracks into a new blank session and copying the media files that way.