I’ve found a few files for which:
- Video LAN for Windows was playing them without any problems (after a 1 second glitch),
- Winamp for Windows was playing them also without problems, but showing 00:00 as each file’s duration
- mobile player for Android failed to play them showing Cannot play content error.
I have downloaded “full version” (130 kilobytes!) meaning — with Windows GUI. Which turned out to be totally not needed as the command line approach did all the job just great.
- Unpack mp3val-0.1.8_with_frontend-0.1.1-bin-win32.zip to any folder
- Copy your not working .mp3 file to the same folder
- Right-click Start button and pick Command Prompt (admin) item
cd [folder name]to navigate to your folder
mp3valwith correct set of switches.
mp3val on.mp3 -lout.log -f -t -nb
on.mp3is your file to by analysed and fixed
-lout.logdenotes that you want to see log of operation in out.log file (notice no space before file name!)
-ftells mp3val to automatically fix any error it finds and can fix
-tinstructs it to give the resulting (fixed) file the same date and time as the original (broken) one
-nbstands for “no backup” and does what it says.
Since we copied corrupted file from its original location (and renamed it to on.mp3 for easier command-line invocation) we can simply ignore all the backup files.
And… that was all. Two seconds ago my one hour long .mp3 file was fixed. Looking into out.log told me that:
WARNING: "C:\m3v\on.mp3" (offset 0x30801): MPEG stream error, resynchronized successfully INFO: "C:\m3v\on.mp3": 146295 MPEG frames (MPEG 1 Layer III), +ID3v1+ID3v2, Xing header FIXED: "C:\m3v\on.mp3": File was rebuilt
As a result, I had a slightly smaller file had correct file length in Winamp and was played by my mobile Android player without any problems.