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. --- video/mp_image.c | 1 + 1 file changed, 1 insertion(+) (limited to 'video/mp_image.c') diff --git a/video/mp_image.c b/video/mp_image.c index 6ab3b87150..8aa3aa025c 100644 --- a/video/mp_image.c +++ b/video/mp_image.c @@ -508,6 +508,7 @@ void mp_image_copy_attributes(struct mp_image *dst, struct mp_image *src) dst->params.color = src->params.color; dst->params.chroma_location = src->params.chroma_location; dst->params.spherical = src->params.spherical; + dst->nominal_fps = src->nominal_fps; // ensure colorspace consistency if (mp_image_params_get_forced_csp(&dst->params) != mp_image_params_get_forced_csp(&src->params)) -- cgit v1.2.3