Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Contribute to GitLab
Sign in / Register
Toggle navigation
F
ffmpeg.wasm-core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Linshizhi
ffmpeg.wasm-core
Commits
602ac487
Commit
602ac487
authored
May 11, 2017
by
James Almer
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc/libav-merge: mention the skipped AVFrame crop fields usage commits
parent
fc63d5ce
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
0 deletions
+5
-0
libav-merge.txt
doc/libav-merge.txt
+5
-0
No files found.
doc/libav-merge.txt
View file @
602ac487
...
...
@@ -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:
------------------------------------------
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment