GNOME Bugzilla – Bug 94726
gnome-volume-control doesn't pick up changes made by other tools
Last modified: 2004-12-22 21:47:04 UTC
See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=74929
This has been reported a long time ago in debian as well. Any idea when (if ever) it will be fixed?
This is borderline high; it makes it hard to use gnome with other things.
Apparently still in GNOME 2.2
*** Bug 82617 has been marked as a duplicate of this bug. ***
Mass reassigning to component owner.
Still in 2.3.5
Ronald, still in 2.6. Looks like a prime candidate for us to tackle, no ? :)
Yes. I've got signal callbacks in the structs, I just didn't implement them. I'm planning to.
*** Bug 143872 has been marked as a duplicate of this bug. ***
Created attachment 28855 [details] [review] make mixer.c respond to volume-changed signal This should make gnome-volume-control react properly to the volume-changed signal of GstMixerTrack. This signal still needs implementing in gstreamer though! I tested using the gst_mixer_volume_changed function to emit the signal, and it seems to work okay, with the exception of unlocked tracks (that is, with different left/right volumes). However, this appears to be broken in the rest of the program as well, so I don't think it's my fault. Should it be relevant, I'm using the OSS sink.
Hi, I mentioned the callbacks and you implemented them. You rightly noticed that the GStreamer plugins didn't actually implement those. Now, there was a reason for the signals being there (assuming that was the right way) and them not being implemented (time). I recently tried implementing them and - as you might notice from the way in which I'm telling it - it didn't work. The reason for that is that I depend on polls (or in libalsa's case: event update notifications) which I need to set up myself, and I actually need to call into libalsa in order for those to be called. Especially in the case of libalsa, I didn't know and didn't expect this. Knowing this, signals are an over-complicated way of solving an issue that a simple g_timeout_add() can do much better. #151971 contains a new volume control which includes g_timeout_add()-based update notifications. It needs no changes in gst-plugins and is, imo, currently the best solution to this problem.
*** This bug has been marked as a duplicate of 151971 ***