A NleOperation performs a transformation or mixing operation on the data from one or more NleSource, which is used to implement filters or effects.
- Maps the time
0. So initial time-shifting effects are excluded (the inpoint can sometimes be used instead).
- Is monotonically increasing. So reversing effects, and effects that jump backwards in the stream are excluded.
- Can handle a reasonable GstClockTime, relative to the project. So this would exclude a time effect with an extremely large speed-up that would cause the converted GstClockTime seeks to overflow.
- Is 'continuously reversible'. This essentially means that for every seek position found on the sink pad of the element, we can, to 'good enough' accuracy, calculate the corresponding seek position that was received on the source pad. Moreover, this calculation should correspond to how the element transforms its GstSegment time field. This is needed so that a seek can result in an accurate segment.
Note that a constant-rate-change effect that is not extremely fast or slow would satisfy these conditions.
For such a time effect, they should be configured in nle such that:
- Their inpoint is
0. Otherwise this will introduce seeking problems in its nlecomposition.
- They must share the same start and duration as all nleobjects of lower priority in its nlecomposition. Otherwise this will introduce jumps in playback.
Note that, at the moment, nle only converts the GstSegment time field which means the other fields, such as start and stop, can end up with non-meaningful values when time effects are involved. Moreover, it does not convert GstBuffer times either, which can result in them having non-meaningful values. In particular, this means that GstControlBinding-s will not work well with nlecomposition-s when they include time effects.
Authors: – Wim Taymans
Rank – none
Plugin – nle
Package – GStreamer Editing Services
Presence – request
Direction – sink
Object type – GstPad
Presence – always
Direction – src
Object type – GstPad
input_priority_changed_callback (GstElement * param_0, GstPad * arg0, guint arg1, gpointer udata)
def input_priority_changed_callback (param_0, arg0, arg1, udata): #python callback for the 'input-priority-changed' signal
Flags: Run Last
Specifies the number of sink pads the operation should provide.
If the sinks property is -1 (the default) pads are only created as
get_request_pad() calls on the element.
Flags : Read / Write
Default value : 1
The results of the search are