SignalRun LasteosSignalRun Lastnew-Signal that a new preroll sample is available.
This signal is emitted from the streaming thread and only when the
"emit-signals" property is true.
The new preroll sample can be retrieved with the "pull-preroll" action
signal or gst_app_sink_pull_preroll() either from this signal callback
or from any other thread.
Note that this signal is only emitted when the "emit-signals" property is
set to true, which it is not by default for performance reasons.
SignalRun Lastnew-Signal that a new sample is available.
This signal is emitted from the streaming thread and only when the
"emit-signals" property is true.
The new sample can be retrieved with the "pull-sample" action
signal or gst_app_sink_pull_sample() either from this signal callback
or from any other thread.
Note that this signal is only emitted when the "emit-signals" property is
set to true, which it is not by default for performance reasons.
SignalRun Lastnew-Signal that a new downstream serialized event is available.
This signal is emitted from the streaming thread and only when the
"emit-signals" property is true.
The new event can be retrieved with the "try-pull-object" action
signal or gst_app_sink_pull_object() either from this signal callback
or from any other thread.
EOS will not be notified using this signal, use GstApp.AppSink::eos instead.
EOS cannot be pulled either, use gst_app_sink_is_eos() to check for it.
Note that this signal is only emitted when the "emit-signals" property is
set to true, which it is not by default for performance reasons.
The callback should return true if the event has been handled, which will
skip basesink handling of the event, false otherwise.
SignalRun Lastpropose-Signal that a new propose_allocation query is available.
This signal is emitted from the streaming thread and only when the
"emit-signals" property is true.
SignalActionRun Lastpull-Get the last preroll sample in appsink. This was the sample that caused the
appsink to preroll in the PAUSED state.
This function is typically used when dealing with a pipeline in the PAUSED state. Calling this function after doing a seek will give the sample right after the seek position.
Calling this function will clear the internal reference to the preroll buffer.
Note that the preroll sample will also be returned as the first sample
when calling gst_app_sink_pull_sample() or the "pull-sample" action signal.
If an EOS event was received before any buffers, this function returns
null. Use gst_app_sink_is_eos () to check for the EOS condition.
This function blocks until a preroll sample or EOS is received or the appsink element is set to the READY/NULL state.
SignalActionRun Lastpull-This function blocks until a sample or EOS becomes available or the appsink element is set to the READY/NULL state.
This function will only return samples when the appsink is in the PLAYING state. All rendered samples will be put in a queue so that the application can pull samples at its own rate.
Note that when the application does not pull samples fast enough, the queued samples could consume a lot of memory, especially when dealing with raw video frames. It's possible to control the behaviour of the queue with the "drop" and "max-buffers" properties.
If an EOS event was received before any buffers, this function returns
null. Use gst_app_sink_is_eos () to check for the EOS condition.
SignalActionRun Lasttry-This function blocks until a sample or an event becomes available or the appsink element is set to the READY/NULL state or the timeout expires.
This function will only return samples when the appsink is in the PLAYING state. All rendered samples and events will be put in a queue so that the application can pull them at its own rate. Events can be pulled when the appsink is in the READY, PAUSED or PLAYING state.
Note that when the application does not pull samples fast enough, the queued samples could consume a lot of memory, especially when dealing with raw video frames. It's possible to control the behaviour of the queue with the "drop" and "max-buffers" properties.
This function will only pull serialized events, excluding
the EOS event for which this functions returns
null. Use gst_app_sink_is_eos() to check for the EOS condition.
This signal is a variant of GstApp.AppSink.SignalSignatures.try_pull_sample | GstApp.AppSink::try-pull-sample: that can be used to handle incoming events as well as samples.
Note that future releases may extend this API to return other object types so make sure that your code is checking for the actual type it is handling.
SignalActionRun Lasttry-Get the last preroll sample in appsink. This was the sample that caused the
appsink to preroll in the PAUSED state.
This function is typically used when dealing with a pipeline in the PAUSED state. Calling this function after doing a seek will give the sample right after the seek position.
Calling this function will clear the internal reference to the preroll buffer.
Note that the preroll sample will also be returned as the first sample
when calling gst_app_sink_pull_sample() or the "pull-sample" action signal.
If an EOS event was received before any buffers or the timeout expires,
this function returns null. Use gst_app_sink_is_eos () to check for the EOS
condition.
This function blocks until a preroll sample or EOS is received, the appsink element is set to the READY/NULL state, or the timeout expires.
SignalActionRun Lasttry-This function blocks until a sample or EOS becomes available or the appsink element is set to the READY/NULL state or the timeout expires.
This function will only return samples when the appsink is in the PLAYING state. All rendered samples will be put in a queue so that the application can pull samples at its own rate.
Note that when the application does not pull samples fast enough, the queued samples could consume a lot of memory, especially when dealing with raw video frames. It's possible to control the behaviour of the queue with the "drop" and "max-buffers" properties.
If an EOS event was received before any buffers or the timeout expires,
this function returns null. Use gst_app_sink_is_eos () to check
for the EOS condition.
SignalDetailedRun Firstdeep-The deep notify signal is used to be notified of property changes. It is typically attached to the toplevel bin to receive notifications from all the elements contained in that bin.
SignalDetailedRun Firstdeep-The deep notify signal is used to be notified of property changes. It is typically attached to the toplevel bin to receive notifications from all the elements contained in that bin.
SignalDetailedRun Firstdeep-The deep notify signal is used to be notified of property changes. It is typically attached to the toplevel bin to receive notifications from all the elements contained in that bin.
SignalRun Lastno-This signals that the element will not generate more dynamic pads. Note that this signal will usually be emitted from the context of the streaming thread.
SignalDetailedActionRun FirstnotifyThe notify signal is emitted on an object when one of its properties has
its value set through g_object_set_property(), g_object_set(), et al.
Note that getting this signal doesn’t itself guarantee that the value of
the property has actually changed. When it is emitted is determined by the
derived GObject class. If the implementor did not create the property with
GObject.ParamFlags.EXPLICIT_NOTIFY, then any call to g_object_set_property() results
in ::notify being emitted, even if the new value is the same as the old.
If they did pass GObject.ParamFlags.EXPLICIT_NOTIFY, then this signal is emitted only
when they explicitly call g_object_notify() or g_object_notify_by_pspec(),
and common practice is to do that only when the value has actually changed.
This signal is typically used to obtain change notification for a
single property, by specifying the property name as a detail in the
g_signal_connect() call, like this:
g_signal_connect (text_view->buffer, "notify::paste-target-list",
G_CALLBACK (gtk_text_view_target_list_notify),
text_view)
It is important to note that you must use [canonical parameter names][class@GObject.ParamSpec#parameter-names] as detail strings for the notify signal.
SignalRun Lastpad-a new Gst.Pad has been added to the element. Note that this signal will
usually be emitted from the context of the streaming thread. Also keep in
mind that if you add new elements to the pipeline in the signal handler
you will need to set them to the desired target state with
gst_element_set_state() or gst_element_sync_state_with_parent().
SignalRun Lastpad-a Gst.Pad has been removed from the element
Signal that the end-of-stream has been reached. This signal is emitted from the streaming thread.