Unfortunatelly we can't change this in the currently used plug-in. The only option is to use another mp3 input plug-in (in_mad?).

Jiri

YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK, YUK!!!!!!!!!!!!!!!!!!!!!

I HATE THE BIT RATE NOT BEING REPORTED PROPERLY IN BETA 4.

This will drive me crazy!
I am so use to watching the bitrate change for VBR songs when they are played.

PLEASE, PLEASE fix this before release...

ah ok, no worries it doesn't actually bother me.

Bitrate reporting currently depends on the input plugin used. In the future, we'll probably make some changes that allow bitrate to be reported in the player via MM in cases where the plugin is inaccurate.

-Rusty

The MM player doesn't report the VBR bitrate as it used to, where it would show the actual bitrate of the part of the song that is playing. Instead it reports the next highest CBR bitrate.