Víctor Manuel Jáquez Leal 8f5933cd80 vaapivideocontext: only vaapisink process app context ... gst.vaapi.app.Display context is made for applications that will provide the VA display and the native display to used by the pipeline, when are using vaapisink as overlay. There are no use case for encoders, decoders, neither for the postprocessor. In the case of the vaapisink, it shall query for gst.vaapi.Display upstream first, and then, if there is no reply, gst.vaapi.app.Display context will be posted in the bus for the application. If the application replies, a GstVaapiDisplay object is instantiated given the context info, otherwise a GstVaapiDisplay is created with the normal algorithm to guess the graphics platform. Either way, the instantiated GstVaapiDisplay is propagated among the pipeline and the have-message bus message. Also only vaapisink will process the gst.vaapi.app.Display, if and only if, it doesn't have a display already set. This is caused because if vaapisink is in a bin (playsink, for example) the need-context is posted twice, leading to an error state. https://bugzilla.gnome.org/show_bug.cgi?id=790999		2017-12-01 23:11:11 +01:00
..
vaapi	vaapivideocontext: only vaapisink process app context	2017-12-01 23:11:11 +01:00
Makefile.am	build: use git.mk	2015-05-18 16:14:46 +02:00
meson.build	vaapi: add meson build	2017-02-09 11:27:44 +01:00