gdkpixbufoverlay breaks vaapi pipeline

[Wolfgang Grandegger]

Hello,

Am 01.05.19 um 15:44 schrieb Nicolas Dufresne:
> 
> 
> Le mer. 1 mai 2019 05 h 51, Wolfgang Grandegger <wg at grandegger.com
> <mailto:wg at grandegger.com>> a écrit :
> 
>     Hello,
> 
>     Am 01.05.19 um 02:12 schrieb Nicolas Dufresne:
>     >
>     >
>     > Le mar. 30 avr. 2019 16 h 25, Wolfgang Grandegger
>     <wg at grandegger.com <mailto:wg at grandegger.com>
>     > <mailto:wg at grandegger.com <mailto:wg at grandegger.com>>> a écrit :
>     >
>     >     Hello,
>     >
>     >     I have a wired problem with the following pipeline:
>     >
>     >       $ gst-launch-1.0 udpsrc port=5678 buffer-size=180000000 \
>     >           !
>     image/jpeg,format=Y42B,width=1920,height=1080,framerate=50/1 \
>     >           ! jpegparse disable-passthrough=true
>     >           ! vaapijpegdec \
>     >
>     >
>     > I'm not fully certain, but I believe you might need to add
>     vaapipostproc
>     > here for this use case. VA element don't produce normal memory, the
>     > postproc can fix that 
> 
>     "vaapipostproc" without arguments does *not* help. But I just found out,
>     that
> 
>       "vaapipostproc format=i420 "
> 
> 
> Ok, in theory, a caps filter after with format=I420 should have the same
> effect. We aim at deprecating that property.
> 
> I suspect that the main side effect is that it's no longer passthrough.
> I think it's worth filing a bug report on gitlab. Something isn't quite
> right for this use case.

Done! See:

https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/158

Thanks,

Wolfgang