GNOME Bugzilla – Bug 513857
volume setting delay against player's control
Last modified: 2010-07-09 12:28:56 UTC
Have tried two players (exaile and yauap) using gstreamer alsa plugin, and at both cases the same issue takes place: volume changes after annoying delay (~1 sec) after player's volume control was changed. 'hdsp' alsa driver is in use. Other information:
This is because the volume control is implemented in software by scaling the audio samples that are sent to the device. By default though, the alsa plugin is set to use 200ms of buffering in the audio device - to prevent buffer underruns and dropouts. You can try setting your sound output to 'Custom' and give it a value like 'alsasink buffer-time=100000' or smaller, and you'll get faster volume changes, at the expense of possibly more dropouts. The buffer-time property is in microseconds.
Jan, I have tried even 'buffer-time=50000', but the delay still takes place. And last one is still ~1 sec.
maybe they don't use the gconf settings.
I have also tried with pulse gst plugin and got the same effect. It is difficult to believe at all cases buffer is set to the same size which is appropriate the same big delay. At, say, mpd/alsa or jack cases the issue doesn't exist. If I understand well, hdsp driver has not many 'common' alsa mixer controls. May be it is the reason.
*** Bug 562046 has been marked as a duplicate of this bug. ***
*** Bug 574882 has been marked as a duplicate of this bug. ***
Is this still an issue with current versions of GStreamer. We have a stream volume interface now, which totem/playbin2 etc. will use, so if you use an audio output that implements this (pulseaudio, oss4), it should work immediately.
Closing as OBSOLETE as per comment #7. Please reopen if this is still an issue.