>Here's a nice bug.. lame 3.93 (and from the looks of it, every version >before it..) identifies files based purely on the friggin suffix of the >filename. World-class coding there, guys. (*chuckle*) .... Anyway, I've >managed to control my laughter long enough to post a note about it.
There is no fool proof way to identify an mp3 file. For that matter there is no such thing as an "mp3 file". An mp3 "file" consists of a sequence of one or more mp3 frames. Frames are identified by a frame sync, and this is nothing more than 11 sequential bits which are all set (1's) starting at a byte boundary. An mp3 frame header is 32-bits long. An mp3 decoder is supposed to consume data, skipping it until it finds a frame sync and then you have a valid frame. So long as this 'other' data does not have any false frame sync's then the mp3 decoder will operate properly. There is nothing an mp3 decoder can do about a false frame. ID3 V2 works using the fact that mp3 decoders will consume data until a frame sync in found. Remember that ID3 V2 tags are at the front of the data file. ID3 V2 gaurantees that a false sync will never be generated. So how does a world class programmer write code to detect a valid mp3 data sequience in a foolproof manner. Norman _______________________________________________ mp3encoder mailing list [EMAIL PROTECTED] http://minnie.tuhs.org/mailman/listinfo/mp3encoder
