MultipartDemux uses the Content-type field of incoming buffers to demux and push data to dynamic source pads. Most of the time multipart streams are sequential JPEG frames generated from a live source such as a network source or a camera.
The output buffers of the multipartdemux typically have no timestamps and are usually played as fast as possible (at the rate that the source provides the data).
the content in multipart files is separated with a boundary string that can be configured specifically with the “boundary” property otherwise it will be autodetected.
gst-launch-1.0 filesrc location=/tmp/test.multipart ! multipartdemux ! image/jpeg,framerate=\(fraction\)5/1 ! jpegparse ! jpegdec ! videoconvert ! autovideosink
|Wim Taymans <firstname.lastname@example.org>, Sjoerd Simons <email@example.com>|
The opaque GstMultipartDemux structure.
“boundary” gchar *
The boundary string separating data, automatic if NULL.
Flags: Read / Write / Construct
Default value: NULL
Assume that there is only one stream whose content-type will not change and emit no-more-pads as soon as the first boundary content is parsed, decoded, and pads are linked.
Flags: Read / Write
Default value: FALSE