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 639216 - controller: add API for elements to get future property values
controller: add API for elements to get future property values
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal enhancement
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-01-11 15:23 UTC by Rob Clark
Modified: 2011-01-11 20:19 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
[PATCH] controller: API for elements to "peek" future values (5.40 KB, patch)
2011-01-11 15:24 UTC, Rob Clark
rejected Details | Review

Description Rob Clark 2011-01-11 15:23:41 UTC
Intended for use by elements that need to see property changes for future
timestamp values.

For example bracketing camera src which needs to pre-program the hardware or
driver for exposure (or other) settings so that the settings change can be
properly synchronized with the capture.
Comment 1 Rob Clark 2011-01-11 15:24:51 UTC
Created attachment 178043 [details] [review]
[PATCH] controller: API for elements to "peek" future values
Comment 2 Stefan Sauer (gstreamer, gtkdoc dev) 2011-01-11 15:56:22 UTC
The point of gst_controller_sync_values() is that the value can be taken from the normal property and the app can also see the current value.
If we need multiple values we could use gst_controller_get_value_arrays(). The element can preparse the data-structures and reuse them.
Comment 3 Sebastian Dröge (slomo) 2011-01-11 17:24:33 UTC
I have to agree with Stefan... can we close this bug as NOTABUG then?
Comment 4 Rob Clark 2011-01-11 18:45:20 UTC
maybe..  at first glance it looks like this could work.  But unless I'm overlooking something, I think then we'd need to add an API to find the names of the controlled properties.
Comment 5 Sebastian Dröge (slomo) 2011-01-11 19:12:32 UTC
Take a look at the volume element, which does exactly what you want :)

gst_object_get_control_source (G_OBJECT (self), property_name) returns NULL if the property is not controlled.
Comment 6 Rob Clark 2011-01-11 19:44:32 UTC
Having something like gst_object_get_controlled_properties() might be nice, but I guess there is a finite set of properties that would be controllable so I guess it is not strictly needed.
Comment 7 Stefan Sauer (gstreamer, gtkdoc dev) 2011-01-11 20:19:41 UTC
Well the element itself will know which ones are controllable :) Apps should just loop over them. there is no API for g_object_class_get_writable_properties() either.