but one track keeps showing me info that it's only got 96 kbit/s. When I listen to it though it's of the same high quality as the others. Any ideas what that's all about?
thanks.
PS Using Max 0.7.2b
I ripped some CDs in LAME 3.97 Variable Bitrate ...
thanks for the quick reply
I also failed to mention that the track only has a running time of 8:04 minutes although it gets shown as having a duration of 18:47 minutes.

so there's no way to manually set a minimum bitrate in Max?
another thingy I find interesting is that what iTunes normally shows me about the track info for tracks created with Max:

Encoded with: LAME 3.97
But in the case of this one file:

Encoded with: LAME 3.97 (Max 0.7.2b)
All of my MP3s are ripped as follows:

thanks for your help and for Max


so there's no way to manually set a minimum bitrate in Max?
another thingy I find interesting is that what iTunes normally shows me about the track info for tracks created with Max:

Encoded with: LAME 3.97
But in the case of this one file:

Encoded with: LAME 3.97 (Max 0.7.2b)
All of my MP3s are ripped as follows:

thanks for your help and for Max

Last edited by chicken on Wed May 02, 2007 4:46 pm, edited 2 times in total.
I just got my hands on a niffty little application called VBRfix which did in fact fix the MP3 created by Max. It now has a proper running time and it shows up as having 223 kbps VBR.

I'll gladly send you the track as a FLAC file so that you can test it with Max as to why the file always gets a bit messy in Max. Just let me know.

I'll gladly send you the track as a FLAC file so that you can test it with Max as to why the file always gets a bit messy in Max. Just let me know.
This is strange- if I encode using the default LAME settings for Max, everything comes out perfectly. If I use your settings, I'm able to duplicate the behavior you describe. I get the following error on tagging: "TagLib: TagLib::ID3v2::Header::parse() - One of the size bytes in the id3v2 header was greater than the allowed 128." I assume LAME is writing something it shouldn't be for your combination of settings. I will look into this a little more.