On Wed May 24 18:24:39 2023 +0000, Paul Gofman wrote:
Rémi may probably answer with more facts and issues with decodebin, but what I observed previously vaadecodebin ignores low-latency parameter while the actual vaapi h264 decoder minds that.
It's a sub-pipeline and it adds all sort of complexity that we don't want to bother with for wg_transform. Threading being one major issue as we want as much control as possible over the processing of samples, ideally making it synchronously.
The wg_transform interface is (ideally) meant to be a synchronous wrapper over decoders / converters, with all the threading problems moved over the user side where we control every detail.