vf_vavpp: get rid of mp_refqueue_is_interlaced()

This makes the difference between passing VA_FRAME_PICTURE or
VA_BOTTOM_FIELD for progressive frames (that should be force-
deinterlaced) to VAProcPipelineParameterBuffer.flags. VA-VPP doesn't
really seem to care, and we can get rid of mp_refqueue_is_interlaced()
entirely. It could be argued it's better to pass field flags instead of
the progressive flag.

1 files changed, 0 insertions, 9 deletions

diff --git a/video/filter/refqueue.c b/video/filter/refqueue.c
index 04de3124a4..6b2e5a2110 100644
--- a/video/filter/refqueue.c
+++ b/video/filter/refqueue.c
@@ -75,15 +75,6 @@ bool mp_refqueue_should_deint(struct mp_refqueue *q)
            !(q->flags & MP_MODE_INTERLACED_ONLY);
 }
 
-// Whether the current output frame is marked as interlaced.
-bool mp_refqueue_is_interlaced(struct mp_refqueue *q)
-{
-    if (!mp_refqueue_has_output(q))
-        return false;
-
-    return q->queue[q->pos]->fields & MP_IMGFIELD_INTERLACED;
-}
-
 // Whether the current output frame (field) is the top field, bottom field
 // otherwise. (Assumes the caller forces deinterlacing.)
 bool mp_refqueue_is_top_field(struct mp_refqueue *q)