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 797052 - alsasink: Changing the device property passed READY state is not supported
alsasink: Changing the device property passed READY state is not supported
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
1.x
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2018-08-30 10:50 UTC by Francesco Ceruti
Modified: 2018-11-03 12:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Francesco Ceruti 2018-08-30 10:50:29 UTC 
Trying to change the "device" property of an alsasink element, after the pipeline is set to "READY", has no actual effect on the used ALSA device.

I've briefly looked at the gstaudiosink.c source, and as far as I can tell,
in the "gst_alsasink_set_property" function, the property value (GstAlsaSink->device) is changed,
but the real ALSA device reference (GstAlsaSink->handle) is not.
Comment 1 Nicolas Dufresne (ndufresne) 2018-08-30 12:21:09 UTC 
Yes, this isn't supported. It is also unlikely going to be supported considering it's harder to implement then replacing the source at application level.
Comment 2 Tim-Philipp Müller 2018-08-30 12:34:55 UTC 
I think this is a WONTFIX, you should be able to change device on the fly with pulseaudio and pulsesrc.
Comment 3 Francesco Ceruti 2018-08-30 14:11:24 UTC 
Okay, as I suspected.
Can this be made clear in the documentation?

Thanks :-)
Comment 4 GStreamer system administrator 2018-11-03 12:09:46 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-base/issues/481.