From c99d95ac17364c46bc161867d1102361f05a6cc5 Mon Sep 17 00:00:00 2001 From: wm4 Date: Sun, 12 Apr 2020 21:55:35 +0200 Subject: vf_format: add gross mechanism for forcing scaler for testing This sucks, but is helpful for testing. Obviously, it would be much nicer if there were a way to specify _all_ scaler options per filter (if the user wanted), instead of always using the global options. But this is "too hard" for now. For testing, it is extremely convenient to select the scaler backend, so add this option, but make clear that it could go away. We'd delete it once there is a better mechanism for this. --- filters/f_autoconvert.h | 3 +++ 1 file changed, 3 insertions(+) (limited to 'filters/f_autoconvert.h') diff --git a/filters/f_autoconvert.h b/filters/f_autoconvert.h index 7cb144aa59..6d6660c46a 100644 --- a/filters/f_autoconvert.h +++ b/filters/f_autoconvert.h @@ -1,6 +1,7 @@ #pragma once #include "filter.h" +#include "video/sws_utils.h" struct mp_image; struct mp_image_params; @@ -12,6 +13,8 @@ struct mp_autoconvert { // f->pins[0] is input, f->pins[1] is output struct mp_filter *f; + enum mp_sws_scaler force_scaler; + // If this is set, the callback is invoked (from the process function), and // further data flow is blocked until mp_autoconvert_format_change_continue() // is called. The idea is that you can reselect the output parameters on -- cgit v1.2.3