summaryrefslogtreecommitdiff
path: root/doc/libav-merge.txt
diff options
context:
space:
mode:
authorJames Almer <jamrial@gmail.com>2017-05-11 14:03:41 -0300
committerJames Almer <jamrial@gmail.com>2017-05-11 14:03:41 -0300
commit602ac487205e04426b49eac0d767f338e3ffcaa4 (patch)
tree22539d6247b99f8f40589b181d391ea598ba54f6 /doc/libav-merge.txt
parentfc63d5ceb357c4b760cb02772de0b50d0557140f (diff)
doc/libav-merge: mention the skipped AVFrame crop fields usage commits
Diffstat (limited to 'doc/libav-merge.txt')
-rw-r--r--doc/libav-merge.txt5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/libav-merge.txt b/doc/libav-merge.txt
index 82aea8e0df..5ae7ce855b 100644
--- a/doc/libav-merge.txt
+++ b/doc/libav-merge.txt
@@ -99,6 +99,11 @@ Stuff that didn't reach the codebase:
- Read aac_adtstoasc extradata updates from packet side data on Matroska once mov and the bsf in question are fixed (See 13a211e632 and 5ef1959080)
- new bitstream reader (see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/209609.html)
- use of the bsf instead of our parser for vp9 superframes (see fa1749dd34)
+- use of the new AVFrame crop fields in h264/hevc/theora (see https://ffmpeg.org/pipermail/ffmpeg-devel/2017-May/211239.html)
+ - a02ae1c683 hevcdec: export cropping information instead of handling it internally
+ - 4fded0480f h264dec: be more explicit in handling container cropping
+ - c3e84820d6 h264dec: export cropping information instead of handling it internally
+ - 1202b71269 theora: export cropping information instead of handling it internally
Collateral damage that needs work locally:
------------------------------------------