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 154207 - playback issue of some files
playback issue of some files
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: dont know
0.3.3
Other other
: Normal normal
: 0.8.5
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-09-30 23:10 UTC by kayalion
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description kayalion 2004-09-30 23:10:32 UTC
Distribution: Debian 3.1
Package: GStreamer
Severity: normal
Version: GNOME2.6.1 unspecified
Gnome-Distributor: Debian
Synopsis: playback issue of some files
Bugzilla-Product: GStreamer
Bugzilla-Component: don't know
Bugzilla-Version: unspecified
Description:
Description of Problem:
The playback of some of my mp3's is at double speed :-(. This happens
when I play them with rhythmbox. When I play them with XMMS, the
playback is normal. I read on planet gnome to report this issue so ... tadaa

Steps to reproduce the problem:
1. play the mp3's with rhythmbox

Actual Results:
playback at double speed

Expected Results:
normal playback

How often does this happen?
always with those files

Additional Information:




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-30 19:10 -------


Unknown version unspecified in product GStreamer. Setting version to "0.3.3".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "GStreamer".
   Setting to default milestone for this product, 'HEAD'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was kayalion@kayalion.net.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Ronald Bultje 2004-10-01 11:57:20 UTC
I fixed that several days/weeks ago, it was a mad plugin bug.