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 346975 - wrong duration for vbr mp3
wrong duration for vbr mp3
Status: RESOLVED DUPLICATE of bug 334192
Product: rhythmbox
Classification: Other
Component: playback
0.9.5
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-08 11:10 UTC by Sven Arvidsson
Modified: 2006-07-11 07:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14

Attachments
VBR mp3 (400.00 KB, audio/mpeg)
2006-07-08 11:11 UTC, Sven Arvidsson 		Details

Description Sven Arvidsson 2006-07-08 11:10:42 UTC 
This bug was reported to the Debian BTS.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354519

The duration for the attached mp3 file is not displayed correctly in Rhythmbox. Totem (Gstreamer backend) seems to display the duration correct.

The file was created with Sound-Juicer and the LAME plugin.
Comment 1 Sven Arvidsson 2006-07-08 11:11:25 UTC 
Created attachment 68617 [details]
VBR mp3
Comment 2 Alex Lancaster 2006-07-08 23:04:44 UTC 
I can duplicate this in HEAD.  Interestingly, when I open this file in totem, I see the the total time flash:

0:00 / 1:42 

(which is what rhythmbox shows) then it quickly resets to:

0:00 / 0:14

which leads me to suspect that there is some issue in the gstreamer backend.
Comment 3 Alex Lancaster 2006-07-08 23:14:25 UTC 
Banshee and quodlibet (using the gstreamer 0.10 backend) also display the incorrect 1:42 time.
Comment 4 James "Doc" Livingston 2006-07-11 07:30:27 UTC 
This is a duplicate of bug 334192.

That track lack any metadata indicating the duration, so GStreamer has to guess. The guess is based on the amount of data it's seen and the file size, but as it's done in the PAUSED state it has very little data to go on, and that data is of a lower bitrate so GStreamer over-guesses.

*** This bug has been marked as a duplicate of 334192 ***