After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 632517 - MP3 variable bit rates are reported incorrectly.
MP3 variable bit rates are reported incorrectly.
Status: RESOLVED DUPLICATE of bug 553468
Product: rhythmbox
Classification: Other
Component: general
0.12.x
Other Linux
: Normal minor
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-10-19 03:30 UTC by jason
Modified: 2010-10-21 03:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description jason 2010-10-19 03:30:36 UTC 
Rhythmbox isn't calculating vbr correctly. It reports most v0 tracks to be 96 kbps, and some a little higher. I can verify with mediainfo and Totem (also gstreamer) that the true bitrate is over 200 Kbps for every track.

CBR and Lossless are reported fine.

Rhythmbox 0.12.8
GStreamer Core Library version 0.10.28
2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 GNU/Linux

This is my first bug report. What other info should I provide?
Comment 1 Jonathan Matthew 2010-10-21 00:42:05 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 553468 ***
Comment 2 jason 2010-10-21 02:45:41 UTC 
No, this is different. The source of the problem may be the same, but every comment in bug 553468 is about track length. I'm talking about the bitrate reported in the "Quality" column.

Track properties in rhythmbox:
File Name: 01 War.mp3
Duration: 3:27
Bitrate: 96 kbps

Mediainfo:
Complete name                    : 01 War.mp3
Duration                         : 3mn 27s
Overall bit rate                 : 215 Kbps

Track length is not my issue. It's bitrate.
Comment 3 Jonathan Matthew 2010-10-21 03:17:45 UTC 
It has the same underlying cause, so it's the same bug.