Hi All,

I am ripping using EAC and LAME 3.97 (-V 0 --vbr-new --add-id3v2 --ignore-tag-errors --ta "%a" --tt "%t" --tg "%m" --tl "%g" --ty "%y" --tn "%n" %s %d) and all of my recent tracks are showing very high (~500) bitrates in Windows Explorer. In ALsong, they show the correct bitrates (~200). Does anyone know what the problem could be? I've enabled "Add IDv3 Tag" in EACs compression options. I also checked "Additionally write ID3v2 tags with padding of 4 kb".

Does anyone know what's up with this? My other files show accurate bitrates.

Thanks!

Kyle

It's just a Windows thing; nothing to worry about. I'm sure a more technical explanation has already been offered since this has been discussed several times before.

Windows is buggy.

Interesting, I searched but I couldn't find anything. Google and the forum. Can you direct me to any threads? I am interested to read what has been said.

It seems wierd that only the ripped audio has buggy bitrate values. Windows handles everything else fine on my computer.

I don’t know if any of them offer a good explanation, but here is a few threads:

http://www.google.com/search?q=vbr+bitrate...drogenaudio.org

I you want vbr bitrate displayed correctly in Windows Explorer, you could use a shell extension:

• http://www.softpointer.com/AudioShell.htm (supports all common formats)
• http://win32lab.com/fsw/mp3infp/ (it would be my favourite in XP if it supported FLAC)
• http://www.mutschler.de/mp3ext/ (only MP3)

Thanks, I did have some interest in AudioShell, so I'm still debating whether or not to download that.

I will check out your other suggestions.

Thanks!