Skip to content

F
ffmpeg
Commit 3c3d4ce4 authored by Michael Niedermayer's avatar Michael Niedermayer
Browse files
Options

doc: fix bistream typo 

Signed-off-by: 's avatarMichael Niedermayer <michael@niedermayer.cc>
parent 80a3227b
Hide whitespace changes
Inline Side-by-side
Showing with 1 addition and 1 deletion
doc/libav-merge.txt
View file @ 3c3d4ce4
...@@ -97,7 +97,7 @@ Stuff that didn't reach the codebase: ...@@ -97,7 +97,7 @@ Stuff that didn't reach the codebase:
- VAAPI VP8 decode hwaccel (currently under review: http://ffmpeg.org/pipermail/ffmpeg-devel/2017-February/thread.html#207348) - VAAPI VP8 decode hwaccel (currently under review: http://ffmpeg.org/pipermail/ffmpeg-devel/2017-February/thread.html#207348)
- Removal of the custom atomic API (5cc0057f49, see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-March/209003.html) - Removal of the custom atomic API (5cc0057f49, see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-March/209003.html)
- Read aac_adtstoasc extradata updates from packet side data on Matroska once mov and the bsf in question are fixed (See 13a211e632 and 5ef1959080) - 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 bistream reader (see http://ffmpeg.org/pipermail/ffmpeg-devel/2017-April/209609.html) - 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 bsf instead of our parser for vp9 superframes (see fa1749dd34)
Collateral damage that needs work locally: Collateral damage that needs work locally:
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment