Printable Version of Topic
-Brading Software Message Board +--Forum: Mp3/Tag Studio Support and Bug Reports +---Topic: repair tool in mo3tag studio started by TGB72 Posted by: TGB72 on Mar. 24 2006,10:48 Hi, I really like the repair feature in mp3tag but why it doesn't keep the vbr quality flag (for example 78 in files encoded using alt preset standard) instead add "1" as quality value for all? Otherwise looks like the repair tool doesn't solve some unusual vbr problems like for example the lame tag encoded at wrong position (some early versions of eac created this kind of problems)... I could send u a little mp3 sample with this error if you want. thanks in advance ![]() Posted by: Magnus Brading on Mar. 26 2006,23:54 I think this "quality" value might have been added (and maybe even only unofficially by some encoder?) after the first "specification" of the Xing VBR frame, and that's why it is not supported. Which program(s) can display this value, and do you perhaps have any other reference info about it? Posted by: TGB72 on Mar. 29 2006,15:50 The VBR quality value is part of the info that comes in the lame tag, both, lame and xing headers are encoded at first by the official lame codec (mainly 3.9x +) if the encoder that handles the lame codec make use of this feature, among other things the lame header contains info like quality, vbr method, lowpass filter, psycho acoustic model, stereo mode, freq, etc. Here you can find someting about this, the info is a little old since is about lame's tag v3.88 (now it goes by v3.97) but even there the VBR quality value is mentioned. Otherwise I'm using encspot pro 2.1 to see the lame tag. Posted by: TGB72 on Mar. 29 2006,16:13 I forgot to post the link, sorry < http://gabriel.mp3-tech.org/mp3infotag.html > Posted by: Magnus Brading on Mar. 30 2006,22:30 Ah, so it was a LAME specific value after all, that's what I thought. Currently only original VBR headers are supported in Mp3/Tag Studio, not LAME-specific headers since it's only one encoder out of many. These might be supported in a future version though, so please stay tuned. end |