GNOME Bugzilla – Bug 545932
mixers that use gst_mixer_set_volume() do not function properly
Last modified: 2009-10-20 17:25:37 UTC
Original bug at Ubuntu: https://bugs.launchpad.net/ubuntu/+bug/252237 The problem is, the volume control skips around and jumps to zero sometimes when adjusting it. I limited the problem down to the ext/alsa directory of gst-plugins-base. The problem is introduced sometime between 0.10.12 and 0.10.14 or at 0.10.14, and it still exists in 0.10.18. I believe this commit is at fault: http://cgit.freedesktop.org/~bilboed/gst-plugins-base/commit/?id=897b0d64cb195450d3a0024a18151d2fbde46a7f
Very likely related to http://bugzilla.gnome.org/show_bug.cgi?id=478512 and dupes of that. Preliminary patch was posted at the Ubuntu bug. It basically reverts that commit. I'm not sure that that is the most ideal solution.
Updated URL for what I believe is the same commit: http://cgit.freedesktop.org/~bilboed/gst-plugins-base/commit/?id=79c63472672df2aa167300f9a3748fb2cc56c32a
(In reply to comment #2) > Updated URL for what I believe is the same commit: > http://cgit.freedesktop.org/~bilboed/gst-plugins-base/commit/?id=79c63472672df2aa167300f9a3748fb2cc56c32a That URL is for one of our test git conversion repositories. The canonical copy is still in CVS, for now.
Where can I find the CVS repository online?
http://cvs.freedesktop.org/gstreamer/gst-plugins-base/
Alright, so the accurate URL is: http://webcvs.freedesktop.org/gstreamer/gst-plugins-base/ext/alsa/gstalsamixer.c?r1=1.37&r2=1.38 So, how do we go about figuring out why this causes the volume controls to behave erratically? (I'm obviously not an expert on the GStreamer code.)
I just filed http://bugzilla.gnome.org/show_bug.cgi?id=570378 which seems closely related, if not entirely the same bug.
Isn't this a duplicate of bug #478512
Could someone please try with a current core/base? I think this was fixed a while back..
I don't get the issue anymore with 0.10.25. I think Stefan is right and it's a duplicate of #478512 and thus, as you say, fixed.
Ok, let's just mark it as duplicate then. If it's still an issue I'm sure we'll hear about it soon enough. Thanks for following up. *** This bug has been marked as a duplicate of bug 478512 ***
Seems that this is fixed for me since some time Thanks