The GstCaps that will negotiated downstream and will be put on outgoing buffers.
The total duration in nanoseconds of the data stream. If the total duration is known, it is recommended to configure it with this property.
Make appsrc emit the "need-data", "enough-data" and "seek-data" signals. This option is by default enabled for backwards compatibility reasons but can disabled when needed because signal emission is expensive.
The format to use for segment events. When the source is producing timestamped buffers this property should be set to GST_FORMAT_TIME.
When enabled, appsrc will check GstSegment in GstSample which was pushed via gst_app_src_push_sample() or "push-sample" signal action. If a GstSegment is changed, corresponding segment event will be followed by next data flow.
FIXME: currently only GST_FORMAT_TIME format is supported and therefore GstAppSrc::format should be time. However, possibly #GstAppSrc can support other formats.
Instruct the source to behave like a live source. This includes that it will only push out buffers in the PLAYING state.
When set to any other value than GST_APP_LEAKY_TYPE_NONE then the appsrc will drop any buffers that are pushed into it once its internal queue is full. The selected type defines whether to drop the oldest or new buffers.
The maximum amount of buffers that can be queued internally. After the maximum amount of buffers are queued, appsrc will emit the "enough-data" signal.
The maximum amount of bytes that can be queued internally. After the maximum amount of bytes are queued, appsrc will emit the "enough-data" signal.
The maximum amount of time that can be queued internally. After the maximum amount of time are queued, appsrc will emit the "enough-data" signal.
The minimum latency of the source. A value of -1 will use the default latency calculations of #GstBaseSrc.
Make appsrc emit the "need-data" signal when the amount of bytes in the queue drops below this percentage of max-bytes.
The parent of the object. Please note, that when changing the 'parent' property, we don't emit #GObject::notify and #GstObject::deep-notify signals due to locking issues. In some cases one can use #GstBin::element-added or #GstBin::element-removed signals on the parent to achieve a similar effect.
The total size in bytes of the data stream. If the total size is known, it is recommended to configure it with this property.
The type of stream that this source is producing. For seekable streams the application should connect to the seek-data signal.
When max-bytes are queued and after the enough-data signal has been emitted, block any further push-buffer calls until the amount of queued bytes drops below the max-bytes limit.