diff options
author | Andreas Rheinhardt <andreas.rheinhardt@outlook.com> | 2022-07-11 19:03:12 +0200 |
---|---|---|
committer | Andreas Rheinhardt <andreas.rheinhardt@outlook.com> | 2022-09-15 21:29:59 +0200 |
commit | f0be9129ad14ae3c94849648d3fdfccbbc3d7fc3 (patch) | |
tree | dea804386b9b21a5ebf487eaae708dfd814e670e /libavformat/srtdec.c | |
parent | bffc8f9af1f8e760a63cbc3680ad814b3c1b99ec (diff) | |
download | ffmpeg-f0be9129ad14ae3c94849648d3fdfccbbc3d7fc3.tar.gz |
avcodec/iff: Split extract_header into extradata and packet part
183132872a1d8bc8a32e7fd8f994fa2f1b2d6bfc made the iff demuxer
output extradata and made the decoder parse said extradata.
To make this extradata extensible, it came with its own internal
length field (containing the offset of the palette at the end
of the extradata). Furthermore, in order to support mid-stream
extradata changes, the packets returned by the demuxer also have
such a length field (containing the offset of the actual packet
data). Therefore the packet parsing the extradata accepted its
input from both AVPackets as well as from ordinary extradata.
Yet the demuxer never made use of this "feature": The packet's
length field always indicated that the packet data starts
immediately after the length field.
Later, commit cb928fc448f9566e6f6c28d53fa4c2388e732a2b stopped
appending the length field to the packets' data; of course,
it also stopped searching for extradata in this data.
Instead it added code to parse the packet's header to the function
that parses extradata. This made this function consist of two disjoint
parts, one of which is only reachable if this function is called
from init (when parsing extradata) and one of which is reachable
when parsing packet headers.
Therefore this commit splits this function into two.
Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
Diffstat (limited to 'libavformat/srtdec.c')
0 files changed, 0 insertions, 0 deletions