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 160480 - [alsasink] Sound frames missing
[alsasink] Sound frames missing
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins
0.8.6
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
: 171481 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2004-12-05 03:55 UTC by Laurent Martelli
Modified: 2006-05-17 13:18 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Laurent Martelli 2004-12-05 03:55:23 UTC
If I try to play a sound file using the following command line, a fraction of
second is missing from the audio output:

gst-launch-0.8 filesrc location=<an_mp3_or_ogg_vorbis_file> ! spider ! alsasink

It does not happen with osssink.
Comment 1 Benjamin Otte (Company) 2004-12-10 06:13:27 UTC
How do you figure that out?
I certainly can't hear that a fraction of the audio is missing, so you probably
use a tool for this. Which one?
Comment 2 Ronald Bultje 2004-12-10 06:55:38 UTC
You should be able to see it in the logs, because then timestamps are wrong and
alsa skips (or inserts silence, for that matter).
Comment 3 Laurent Martelli 2004-12-10 15:03:03 UTC
I did not have to use a tool, I just heard it. The fraction of second I'm
talking about is a tenth of second or two so it's hearable. The skipped fragment
is not at the very beginning, but a few tenth of seconds after. It only happens
once and then all is fine.

No silence is inserted, a part of the music is skipped.

I can see no error message on the std output, and I couldn't find any relevent
log file. I used -i to see where the skip is, and it's around iteration #100.

I've played with the buffer-size parameter of alsasink, and it stops skipping at
24576 (8192 * 3) and above.
Comment 4 Christian Fredrik Kalager Schaller 2004-12-21 16:09:27 UTC
Considering the age of this bug, could it be that you have a version where
alsasink consume 100% CPU? (which in turn can cause glitches/hickups in the sound)

If you don't have latest version of gst-plugins please update as a lot of
alsasink related bugs have been taken care of over the last releases.
Comment 5 Laurent Martelli 2004-12-22 00:12:02 UTC
I've tried with CVS today, and the problem is still there. There's nothing
anormal in the CPU usage.
Comment 6 Ronald Bultje 2005-04-09 09:09:12 UTC
*** Bug 171481 has been marked as a duplicate of this bug. ***
Comment 7 Andy Wingo 2006-01-22 15:02:14 UTC
Laurent, ping? How is this situation for you with CVS gst-plugins? Alsasink got some fixes in the last year ;)

I don't think this problem is there with 0.10, but it would also be good to find that out.
Comment 8 Laurent Martelli 2006-01-23 09:05:27 UTC
Hi, I haven't played with gstreamer for a while, but I'll try to find some time to test the latest version against this bug.
Comment 9 Tim-Philipp Müller 2006-05-17 13:17:51 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 10 Tim-Philipp Müller 2006-05-17 13:18:38 UTC
(Sorry, that should have been OBSOLETE :))