From ff24285eb15676dc7519b858be01a1def155e847 Mon Sep 17 00:00:00 2001 From: wm4 Date: Thu, 19 Apr 2018 17:42:14 +0200 Subject: video: pass through container fps to filters This means vf_vapoursynth doesn't need a hack to work around the filter code, and libavfilter filters now actually get the frame_rate field on input pads set. The libavfilter doxygen says the frame_rate field is only to be set if the frame rate is known to be constant, and uses the word "must" (which probably means they really mean it?) - but ffmpeg.c sets the field to mere guesses anyway, and it looks like this normally won't lead to problems. --- filters/f_decoder_wrapper.c | 1 + 1 file changed, 1 insertion(+) (limited to 'filters/f_decoder_wrapper.c') diff --git a/filters/f_decoder_wrapper.c b/filters/f_decoder_wrapper.c index 16b9cd06df..2ad145b5cb 100644 --- a/filters/f_decoder_wrapper.c +++ b/filters/f_decoder_wrapper.c @@ -358,6 +358,7 @@ static void process_video_frame(struct priv *p, struct mp_image *mpi) fix_image_params(p, &mpi->params); mpi->params = p->fixed_format; + mpi->nominal_fps = p->public.fps; mpi->pts = pts; p->pts = pts; -- cgit v1.2.3