Michael Niedermayer 46070cc20a ffmpeg: set muxer packet duration based on framerate only for CFR ...

a set ost->frame_rate does not imply CFR in ffmpeg

The changed fate tests had all wrong packet durations
(like 1/1000 or 1/90000)

There might be more cases in which is_cfr could be set

Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>

2015-11-11 15:04:21 +01:00

..

acodec

libavformat/matroska: Write stream durations in metadata, in the format of mkvmerge.

2015-08-05 22:29:23 +02:00

fate

ffmpeg: set muxer packet duration based on framerate only for CFR

2015-11-11 15:04:21 +01:00

lavf

avformat/mxfenc: Only store user comment related tags when needed

2015-11-10 23:27:51 +01:00

lavf-fate

Merge commit 'ef363ebd596da18f889a7d4845023a23dfac84c9'

2014-10-24 15:30:12 +02:00

seek

avformat/mxfenc: Only store user comment related tags when needed

2015-11-10 23:27:51 +01:00

vsynth

fate: add 10bits YUV4:2:2 dnxhd test

2015-10-13 04:04:02 +02:00

vsynth1

…

vsynth_lena

tests: Rename vsynth2 to vsynth_lena

2014-12-02 03:02:30 +01:00