From 259c71c199e9b4ea89bf4cb90ed0e207ddc9dff7 Mon Sep 17 00:00:00 2001 From: Alex Agranovsky Date: Sun, 29 Nov 2015 18:54:14 -0500 Subject: avformat/mpjpeg: utilize MIME boundary value to detect start of new frame This code is disabled by default so not to regress endpoints sending invalid MIME, but can be enabled via AVOption 'strict_mime_boundary' Signed-off-by: Alex Agranovsky --- doc/demuxers.texi | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'doc/demuxers.texi') diff --git a/doc/demuxers.texi b/doc/demuxers.texi index 349b531357..fb1e4fb3e5 100644 --- a/doc/demuxers.texi +++ b/doc/demuxers.texi @@ -450,6 +450,21 @@ to 1 (-1 means automatic setting, 1 means enabled, 0 means disabled). Default value is -1. @end table +@section mpjpeg + +MJPEG encapsulated in multi-part MIME demuxer. + +This demuxer allows reading of MJPEG, where each frame is represented as a part of +multipart/x-mixed-replace stream. +@table @option + +@item strict_mime_boundary +Default implementation applies a relaxed standard to multi-part MIME boundary detection, +to prevent regression with numerous existing endpoints not generating a proper MIME +MJPEG stream. Turning this option on by setting it to 1 will result in a stricter check +of the boundary value. +@end table + @section rawvideo Raw video demuxer. -- cgit v1.2.3