summaryrefslogtreecommitdiff
path: root/doc/bitstream_filters.texi
diff options
context:
space:
mode:
authorDerek Buitenhuis <derek.buitenhuis@gmail.com>2021-06-23 17:12:43 +0100
committerDerek Buitenhuis <derek.buitenhuis@gmail.com>2021-06-29 15:31:06 +0100
commitd70dde2712bbead523004d8294ff1a0fdeab480b (patch)
tree4f69abe45cca715c9c3b8c58e17f31dea1b77e1e /doc/bitstream_filters.texi
parentb74beba9a9a317caa7ac973cb76cc6ab0ade7667 (diff)
avcodec/h264_metadata_bsf: Allow zeroing constraint_set4_flag and constraint_set5_flag
These bits are reserved in earlier versions of the H.264 spec, and some poor hardware decoders require they are zero. Thus, it is useful to be able to zero these on streams that may have them set. The result is still a valid H.264 bitstream. Signed-off-by: Derek Buitenhuis <derek.buitenhuis@gmail.com>
Diffstat (limited to 'doc/bitstream_filters.texi')
-rw-r--r--doc/bitstream_filters.texi5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/bitstream_filters.texi b/doc/bitstream_filters.texi
index 60e729484d..e3c56f1887 100644
--- a/doc/bitstream_filters.texi
+++ b/doc/bitstream_filters.texi
@@ -253,6 +253,11 @@ Set whether the stream has fixed framerate - typically this indicates
that the framerate is exactly half the tick rate, but the exact
meaning is dependent on interlacing and the picture structure (see
H.264 section E.2.1 and table E-6).
+@item zero_new_constraint_set_flags
+Zero constraint_set4_flag and constraint_set5_flag in the SPS. These
+bits were reserved in a previous version of the H.264 spec, and thus
+some hardware decoders require these to be zero. The result of zeroing
+this is still a valid bitstream.
@item crop_left
@item crop_right