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 748577 - pulsesink: doesn't notify about volume changes in paused state or after connecting to pulseaudio
pulsesink: doesn't notify about volume changes in paused state or after conne...
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-good
1.4.4
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2015-04-28 08:14 UTC by Christoph Reiter (lazka)
Modified: 2018-11-03 15:00 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christoph Reiter (lazka) 2015-04-28 08:14:45 UTC 
Due to flat-volumes I'm exposing the pulsesink volume property in the UI now and noticed some problems:

1) When the pulsesink is created it returns 1.0 for volume and after going to paused it returns the actual volume assigned by PA. notify::volume never gets fired in between.

2) When in playing state, changing the volume in the gnome sound preferences or pavucontrol, pulsesink fires notify::volume. In the paused state it never fires notify::volume but the volume values changes.

I've currently worked this around my polling pulsesink in case of state change messages on the bus and when the user interacts with the volume widget. It would be nice if pulsesink would notify in all cases where volume potentially changes.
Comment 1 Dustin Spicuzza 2015-08-06 03:30:50 UTC 
+1 on fixing this.
Comment 2 Nicolas Dufresne (ndufresne) 2015-08-06 12:45:55 UTC 
(Side note, be aware that these changes will most likely be fired from a non-main thread)
Comment 3 Nicolas Dufresne (ndufresne) 2015-08-06 12:57:15 UTC 

*** This bug has been marked as a duplicate of bug 680779 ***
Comment 4 Christoph Reiter (lazka) 2015-08-06 13:06:41 UTC 
bug 680779 seems unrelated, this is about the volume property not the pulseaudio volume.
Comment 5 Nicolas Dufresne (ndufresne) 2015-08-06 13:19:41 UTC 
Ok ok, let's keep it separate then, but I do believe the part you set about flat-volume is a match. Will you propose a patch ?
Comment 6 Nicolas Dufresne (ndufresne) 2015-08-06 13:22:55 UTC 
For your interest, the point was that you should always be able to set 1.0 to start with, and not get any master volume change (as in GStreamer you should control the stream volume).
Comment 7 Christoph Reiter (lazka) 2015-08-06 13:48:22 UTC 
Thanks.

The problem also occurs without flat-volumes but isn't visible as much as the master volume doesn't affect the stream volume and the user doesn't change the stream volume from outside (pavucontrol, gnome sound settings,..) that often.

I'll look into providing a patch.

(I never set the volume property to some constant, so bug 680779 doesn't affect me..)
Comment 8 GStreamer system administrator 2018-11-03 15:00:08 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/183.