GNOME Bugzilla – Bug 126820
[GST] Alsa problems with 0.6.0
Last modified: 2004-12-22 21:47:04 UTC
I have rhythmbox 0.6.0 and gstreamer 0.7.1 all compiled from official source tarballs with gcc 3.3.2. I'm using alsasink as my output sink (alsa 0.9.7c). When I try to start a song in rb I get no sound even if the progress meter starts running. If I seek using the progress meter and pause/restart I get sound. It won't work unless I seek. After a while (some minutes) it just stops playing although the progress meter is still progressing normally. If I try to press pause (for restarting) rb freezes. On the console I get the following: Allocating 524288 bytes (131072 samples) now to resync: sample 0 expected, but got 33665723 Allocating 524288 bytes (131072 samples) now to resync: sample 131072 expected, but got 33665723
Allright, with gstreamer 0.7.3, rhythmbox 0.6.4 and Alsa 1.0.1 playing now works, kindof. When playing I get sound for the first 24 seconds or so and then nothing (this time is not always the same, just now I got over a minute, which is a new record). The progress meter just keeps going. Stopping and restarting results in the same: first there is sound for and then it just mutes or something. Its doesn't freeze anymore though. Nothing is printed on the console. FYI I uninstalled gstreamer and rhythmbox and all the old libs and plugins and such to get a new clean install, but the problem still remains.
I was told that this could possibly be caused when spider and opt scheduler are added to the pipeline. --gst-scheduler=basicgthread might help. I am going to reassign this bug to the Gstreamer team and mark it as critical.
This is a problem with opt, spider and too many loopbased elements. My idea is that it might have something to do with EOS handling inside spider, but I have not been able to track this down yet.
I tried linux 2.6.3-rc2 with its builtin alsa: same result. Forgetting to run gst-register really gives me grey hairs ... perhaps gstreamers/gst-plugins 'make install' should remind us (the users) to do this?
rhythmbox 0.6.8 + gstreamer 0.7.4 + kernel 2.6.3 with its builtin alsa does not seem to have this problem, at least not for my current session. It also is the first version of rhythmbox which does not crash or freeze after playing around with it for a bit. Good work. Of course if this is a deadlock the bug might not be fixed, but it doesn't trigger for me at the moment.
Btw, I use glib/gtk+ 2.3 now and I used 2.2 before..
..and of course I have to update this bug too early. It still stops playing, but only after a considerably longer time than before (up to 10 minutes).
I use rhythmbox 0.7.2 and gstreamer 0.8.0 and alsa from linux 2.6.5 now and after listening to over an hour of streaming audio and one 40 -minute mp3, I cannot reproduce this.
Do you want me to keep this open or can I close it?
Go ahead an close it, I can always reopen it later can't I?
Yes.