No VASurface after vaapipostproc
While adding wayland support to my gstreamer application (using waylandsink), I noticed excessive CPU use during playback. When I use gst-play to play the same file, the CPU use is much lower, as expected for a vaapi pipeline. I compared the dot-graphs of the two applications and as far as I can see, the only difference is that in mine the output of the GatVaapiPostproc element is not marked as VASurface -- which would explain the CPU use.
If I look at warning level debug output, I can't see anything interesting. If I increase the level, things become very verbose..
Does anyone have any idea what could cause this, or how I can further troubleshoot this? Does this indicate that something is going wrong during pad negotiations of some element?