-Brading Software Message Board
+--Forum: Mp3/Tag Studio Support and Bug Reports
+---Topic: Error in displaying bitrate, length etc... started by mll
Posted by: mll on Nov. 04 2002,10:15
Hi,
I have a file that must be corrupted in some way. MP3TS, as well as Winamp's detailed info say it's 40s long while it's 1'50s (as says winamp's timer). Hence a wrong bitrate displayed (352 instead of 128 kbps, quite logical since 352/110*40=128 ).
The frequency is wrong, too, as well as the layer number and probably other stuff... It's a CBR file FYI.
MP3TS's repair functions change nothing. Does MP3TS allow me to clean this ?
TIA,
MLL
Posted by: Magnus Brading on Nov. 04 2002,14:09
My guess would be that the file is corrupted in a way similar to the file discussed in this thread:
< http://www.magnusbrading.com/cgi-bin....1;t=117 >
Anyway, if you mail me the file, I can take a look at it, and probably fix it manually if you want.
Posted by: Magnus Brading on Nov. 05 2002,15:08
Ok, I've analyzed the file, and found the following errors:
1.
Too large ID3v2 padding (non-fatal).
Is easily fixed with the "Remove junk data before first mp3 frame" repair mode.
2.
Other junk data in the beginning of the file, containing false positives for mp3 frames.
Whenever you get a problem like this, you can perform the following procedure to fix it:
* Temporarily remove the ID3v2 tag (e.g. copy it to the clipboard and then remove it from the file, and then you can paste it back when you're done).
* Open the file in a hex-editor and set the very first byte to 00 (zero).
* Perform the "Remove junk data before first mp3 frame" repair on the file.
* Repeat the two previous steps until the mp3 info is displayed correctly for the file. In the case of this file, I had to repeat it 3 or 4 times.
After this, the file will be fully recovered (now you can paste back the ID3v2 tag from the clipboard).
Posted by: mll on Nov. 05 2002,15:30
Works for me indeed. Thanks ! Now, if all this could be automatic...
MLL
Posted by: Magnus Brading on Nov. 05 2002,15:37
As explained in the thread I referred to above, it is very hard to make an automatic repair process for the cases when the trash data contains sequences that look exactly like genuine mp3-headers...
end