Andreas Rheinhardt 518bbe9eac 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>		2020-03-06 00:58:31 +01:00
..
acodec	avformat/movenc: ensure we don't write the major brand as a compatible brand more than once	2019-12-21 11:57:28 -03:00
fate	h264_mp4toannexb: Try to avoid four byte startcodes	2020-03-06 00:58:31 +01:00
lavf	avformat/mxfenc: use a zero based continuity counter	2020-03-02 22:01:47 +01:00
lavf-fate	fate/lavf-container: add an AV1 in Matroska muxing test	2020-01-26 12:41:32 -03:00
pixfmt
seek	avformat/movenc: ensure we don't write the major brand as a compatible brand more than once	2019-12-21 11:57:28 -03:00
vsynth	avformat/movenc: ensure we don't write the major brand as a compatible brand more than once	2019-12-21 11:57:28 -03:00
vsynth1
vsynth_lena