|
Printable Version of Topic
-Brading Software Message Board +--Forum: Mp3/Tag Studio Support and Bug Reports +---Topic: Reported errors by mp3Utility - maybe OT started by calberga Posted by: calberga on Dec. 28 2007,16:13 This may be off-topic, but perhaps someone can shed some light. I have been using the program mp3Utility to check for "sync errors" (which, usually, seem to indicate data drop-outs). I had been getting some files flags as "Error: Can't locate second frame header for VBRI file" -- note that this in turn seems to be an error, as a new version of mp3Utility has just appeared which doesn't throw this error on the same files). When I saw this I tried running the repair function (with "only real VBR" checked), even though Mp3/TS didn't show an error. The result was that mp3Utility now reports a sync error at 0:00 seconds. Is this some weirdness in mp3Utilities? Or does running the repair on a file (which doesn't show red) change something that could cause this to show? Posted by: Magnus Brading on Jan. 01 2008,14:18 VBR headers are very badly standardized, so it could very likely be some small detail that the two programs have a slightly different opinion about how it should be done. The files still play good in any player, right? Posted by: calberga on Jan. 01 2008,16:01 The play well, and when I let CoolEdit convert them there is no obvious defect at the start. When MP3Utility reports a sync error at any other point in a file I can see a short "flatline" at the location when using CE to examine it. I don't think I have an example of "sync error at 0.0%..." on a file without a silent lead-in, so I can't be sure that there isn't something funny about the files, but since the drop-outs are all very short I doubt that I could hear it in any case. I haven't gotten a response from the author of the program. end |