aboutsummaryrefslogtreecommitdiffstats
path: root/tests/ref/fate/h264-conformance-cvmanl1_toshiba_b
diff options
context:
space:
mode:
authorAndreas Rheinhardt <andreas.rheinhardt@gmail.com>2019-05-17 00:29:51 +0200
committerJames Almer <jamrial@gmail.com>2019-06-23 00:47:50 -0300
commit43c3cebbd4c09dd4d2f9122b38f23eddfe7cadbe (patch)
treec17a5ee3206b86c0ed828f77c025b3909b87e3cd /tests/ref/fate/h264-conformance-cvmanl1_toshiba_b
parent36aceb6174a6a1c40014001ff73c4c30012b569d (diff)
downloadffmpeg-43c3cebbd4c09dd4d2f9122b38f23eddfe7cadbe.tar.gz
avformat/matroskadec: Set offset of first cluster
By default, the data_offset member of the AVFormatInternal of the AVFormatContext associated with the MatroskaDemuxContext has not been initialized explicitly by any Matroska-specific function, so that it was initialized by default to the offset at the end of matroska_read_header, i.e. usually to the offset of the length field of the first encountered cluster. This meant that in case that the Matroska-specific seek-code fails because there are no index entries for the target track a seek to data_offset would be performed and ordinary parsing would start from there which is nonsense: The length field would be treated as EBML ID and (if the length field is not longer than four bytes (EBML numbers that long are rejected as invalid EBML IDs)) whatever comes next would be treated as its EBML size although it simply isn't. Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
Diffstat (limited to 'tests/ref/fate/h264-conformance-cvmanl1_toshiba_b')
0 files changed, 0 insertions, 0 deletions