videoconvertscale: Don't claim we can support any kind of memory
authorThibault Saunier <tsaunier@igalia.com>
Fri, 21 May 2021 22:55:25 +0000 (18:55 -0400)
committerThibault Saunier <tsaunier@igalia.com>
Wed, 20 Apr 2022 21:03:21 +0000 (17:03 -0400)
commitf3fd4d7e90807927e9ddead6b4302c669d99c269
tree911b84b7532c2dee1c222b57d268a99052e21221
parentd11f13f476411b828387c3c26619bc77c255affb
videoconvertscale: Don't claim we can support any kind of memory

Since d0133a2d11566ff4c0cded7af8dfdff0046e0e8b "videoconvert: Allow
passthrough for ANY caps features" videoconvert will always claim that
it supports any kind of memory which is true in very specific case (when
it is running in passthrough mode). To get elements that autoplug
converters depending on the caps running in the pipeline (like
autovideoconvert), we need to have converters no lie about what they can
do when queried `accept_caps` or `query_caps`.

This still accepts any caps feature as before but it introduces
a restriction in the way we handle memory capsfeatures.

We keep previous behaviour in videoconvert and videoscale.

Part-of: <https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/898>
subprojects/gst-plugins-base/gst/videoconvertscale/gstvideoconvert.c
subprojects/gst-plugins-base/gst/videoconvertscale/gstvideoconvertscale.c
subprojects/gst-plugins-base/gst/videoconvertscale/gstvideoconvertscale.h
subprojects/gst-plugins-base/gst/videoconvertscale/gstvideoscale.c