This website requires JavaScript.
Explore
Help
Register
Sign In
virtualenv
/
FFmpeg
Watch
1
Star
0
Fork
0
You've already forked FFmpeg
mirror of
https://github.com/FFmpeg/FFmpeg.git
synced
2024-12-12 19:18:44 +02:00
Code
Issues
Releases
Activity
9e1ffeda8c
FFmpeg
/
tests
/
ref
/
fate
/
h264-bsf-mp4toannexb
2 lines
33 B
Plaintext
Raw
Normal View
History
Unescape
Escape
h264_mp4toannexb: Try to avoid four byte startcodes According to the H.264 specifications, the only NAL units that need to have four byte startcodes in H.264 Annex B format are SPS/PPS units and units that start a new access unit. Before af7e953a, the first of these conditions wasn't upheld as already existing in-band parameter sets would not automatically be written with a four byte startcode, but only when they already were at the beginning of their input packets. But it made four byte startcodes be used too often as every unit that is written together with a parameter set that is inserted from extradata received a four byte startcode although a three byte start code would suffice unless the unit itself were a parameter set. FATE has been updated to reflect the changes. Although the patch leaves the extradata unchanged, the size of the extradata according to the FATE reports changes. This is due to a quirk in ff_h2645_packet_split which is used by extract_extradata: If the input is Annex B, the first zero of a four byte startcode is considered a part of the last unit (if any). Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@gmail.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
2019-12-15 00:19:20 +02:00
5f04c27cc6ee8625fe2405fb0f7da9a3
Reference in New Issue
Copy Permalink