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 159318 - [alsasink/opt] Time presentation is a few seconds off for mp3 in combination with alsasink
[alsasink/opt] Time presentation is a few seconds off for mp3 in combination ...
Status: RESOLVED FIXED
Product: GStreamer
Classification: Platform
Component: gst-plugins
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 158724 160804 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-11-24 15:03 UTC by Christian Fredrik Kalager Schaller
Modified: 2005-11-11 16:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Fredrik Kalager Schaller 2004-11-24 15:03:10 UTC 
Seekbar do not follow sound properly and at EOS the terminal is spewed with:
** (totem:27446): WARNING **: could not link audio/x-raw-int,
endianness=(int)1234, signed=(boolean)true, width=(int)16, depth=(int)16,
rate=(int){ 8000, 11025, 12000, 16000, 22050, 24000, 32000, 44100, 48000 },
channels=(int)[ 1, 2 ]
Comment 1 Ronald Bultje 2004-12-01 14:24:32 UTC 
The warning is a dup of #159269 and is fixed.

The time: I'm unsure. The pipeline is as simple as mad ! audioconvert !
audioscale ! volume ! alsasink. Mad handles the queries correctly. It returns
values as it pushes data out. However, this data doesn't ever arrive at
alsasink, even though the clock is already ticking (up to 6 seconds for
benow.mp3) and mad has pushed those samples out. So it's lagging somewhere in
between, I don't know where. Audioconvert uses a standard chain function, same
for audioscale/volume.

I don't know where it is in between, because if I understand scheduling
correctly, then the chain functions call each other, and alsasink (loop-based)
is in-the-lead. However, and this is important, I don't see this when using
(chain-based) osssink as audio output. Wim, can you tell me what's going on in
between?
Comment 2 Ronald Bultje 2004-12-17 00:09:25 UTC 
*** Bug 158724 has been marked as a duplicate of this bug. ***
Comment 3 Christian Fredrik Kalager Schaller 2005-01-28 15:37:26 UTC 
Seems better for me now. On first playback the streambar jumps a little in the
begining in Totem, but on second run in repeat mode it seems to behave 100% correct.
Comment 4 Ronald Bultje 2005-02-04 09:20:26 UTC 
*** Bug 160804 has been marked as a duplicate of this bug. ***
Comment 5 Ronald Bultje 2005-03-10 18:16:12 UTC 
I can no longer reproduce this. I have probably accidently fixed it. Please confirm.
Comment 6 Luca Ognibene 2005-11-11 16:36:55 UTC 
Closing. Please reopen if it's still an issue.