video: remove vf_vavpp from automatic deinterlace property

This reverts commit 6385a5fd1b8a67c051b82d48c993a6591e8f93c6, and in
addition removes the code that automatically inserts the vavpp filter.

The reason is the same as the commit that is being reverted: this
filter seems to trigger driver bugs. It can cause GPU freezes or
just doesn't work.

This variant of disabling the filter is better. There was no way to
add the "force" parameter to the automatically inserted filter, so
the old approach just made manual filter insertion (with the --vf
option or "vf" command) more cumbersome.

1 files changed, 0 insertions, 9 deletions

diff --git a/video/filter/vf_vavpp.c b/video/filter/vf_vavpp.c
index 02bf783123..8c41ba8734 100644
--- a/video/filter/vf_vavpp.c
+++ b/video/filter/vf_vavpp.c
@@ -54,7 +54,6 @@ struct opts {
     int deint_type;
     int interlaced_only;
     int reversal_bug;
-    int force;
 };
 
 struct priv {
@@ -449,13 +448,6 @@ static struct mp_filter *vf_vavpp_create(struct mp_filter *parent, void *options
 
     p->queue = mp_refqueue_alloc(f);
 
-    if (!p->opts->force) {
-        MP_ERR(f, "This filter is disabled because it is known to cause GPU "
-                  "lockups. This is a driver bug. You can override this by "
-                  "passing force=yes as filter argument.\n");
-        goto error;
-    }
-
     p->av_device_ref = mp_filter_load_hwdec_device(f, AV_HWDEVICE_TYPE_VAAPI);
     if (!p->av_device_ref)
         goto error;
@@ -490,7 +482,6 @@ static const m_option_t vf_opts_fields[] = {
                 {"motion-compensated", 5})),
     OPT_FLAG("interlaced-only", interlaced_only, 0),
     OPT_FLAG("reversal-bug", reversal_bug, 0),
-    OPT_FLAG("force", force, 0),
     {0}
 };