Anton Khirnov 129c7bf53f fftools/ffmpeg: always use the same path for setting InputStream.[next_]dts ... Currently those are set in different ways depending on whether the stream is decoded or not, using some values from the decoder if it is. This is wrong, because there may be arbitrary amount of delay between input packets and output frames (depending e.g. on the thread count when frame threading is used). Always use the path that was previously used only for streamcopy. This should not cause any issues, because these values are now used only for streamcopy and discontinuity handling. This change will allow to decouple discontinuity processing from decoding and move it to ffmpeg_demux. It also makes the code simpler. Changes output in fate-cover-art-aiff-id3v2-remux and fate-cover-art-mp3-id3v2-remux, where attached pictures are now written in the correct order. This happens because InputStream.dts is no longer reset to AV_NOPTS_VALUE after decoding, so streamcopy actually sees valid dts values.		2023-05-02 10:59:24 +02:00
..
acodec	fftools/ffmpeg: propagate frame durations to packets when encoding	2023-04-19 21:12:03 +02:00
fate	fftools/ffmpeg: always use the same path for setting InputStream.[next_]dts	2023-05-02 10:59:24 +02:00
lavf	fftools/ffmpeg: rework audio-decode timestamp handling	2023-05-02 10:59:24 +02:00
lavf-fate	avformat/matroskaenc: support writing Dynamic HDR10+ packet side data	2023-04-08 10:28:41 -03:00
pixfmt
seek	lavf/dv: use a more granular timebase for audio	2023-05-02 10:57:21 +02:00
vsynth	tests: Add more j2k tests to cover a wider range of cases	2023-04-02 23:54:52 +02:00