mpv/audio/decode
wm4 a5b51f75dc demux: get rid of demux_packet.new_segment field
The new_segment field was used to track the decoder data flow handler of
timeline boundaries, which are used for ordered chapters etc. (anything
that sets demuxer_desc.load_timeline). This broke seeking with the
demuxer cache enabled. The demuxer is expected to set the new_segment
field after every seek or segment boundary switch, so the cached packets
basically contained incorrect values for this, and the decoders were not
initialized correctly.

Fix this by getting rid of the flag completely. Let the decoders instead
compare the segment information by content, which is hopefully enough.
(In theory, two segments with same information could perhaps appear in
broken-ish corner cases, or in an attempt to simulate looping, and such.
I preferred the simple solution over others, such as generating unique
and stable segment IDs.)

We still add a "segmented" field to make it explicit whether segments
are used, instead of doing something silly like testing arbitrary other
segment fields for validity.

Cached seeking with timeline stuff is still slightly broken even with
this commit: the seek logic is not aware of the overlap that segments
can have, and the timestamp clamping that needs to be performed in
theory to account for the fact that a packet might contain a frame that
is always clipped off by segment handling. This can be fixed later.
2017-10-24 19:35:55 +02:00
..
ad.h audio: introduce a new type to hold audio frames 2017-08-16 21:10:54 +02:00
ad_lavc.c audio: introduce a new type to hold audio frames 2017-08-16 21:10:54 +02:00
ad_spdif.c audio: introduce a new type to hold audio frames 2017-08-16 21:10:54 +02:00
dec_audio.c demux: get rid of demux_packet.new_segment field 2017-10-24 19:35:55 +02:00
dec_audio.h audio: introduce a new type to hold audio frames 2017-08-16 21:10:54 +02:00