From 15a5d33b7930b53cbc4503053211aee91d6e9659 Mon Sep 17 00:00:00 2001 From: wm4 Date: Wed, 25 May 2016 19:01:32 +0200 Subject: vf_vavpp: move frame handling to separate file Move the handling of the future/past frames and the associated dataflow rules to a separate source file. While this on its own seems rather questionable and just inflates the code, I intend to reuse it for other filters. The logic is annoying enough that it shouldn't be duplicated a bunch of times. (I considered other ways of sharing this logic, such as an uber- deinterlace filter, which would access the hardware deinterlacer via a different API. Although that sounds like kind of the right approach, this would have other problems, so let's not, at least for now.) --- wscript_build.py | 1 + 1 file changed, 1 insertion(+) (limited to 'wscript_build.py') diff --git a/wscript_build.py b/wscript_build.py index 61830b5dff..179d810422 100644 --- a/wscript_build.py +++ b/wscript_build.py @@ -297,6 +297,7 @@ def build(ctx): ( "video/decode/vd_lavc.c" ), ( "video/decode/videotoolbox.c", "videotoolbox-hwaccel" ), ( "video/decode/vdpau.c", "vdpau-hwaccel" ), + ( "video/filter/refqueue.c" ), ( "video/filter/vf.c" ), ( "video/filter/vf_buffer.c" ), ( "video/filter/vf_crop.c" ), -- cgit v1.2.3