GNOME Bugzilla – Bug 770357
list of elements exposed depends on available display at first init
Last modified: 2016-10-31 14:30:13 UTC
Basically, if you compile/install gst-vaapi and then run this from an X terminal: DISPLAY= gst-inspect-1.0 vaapi you get 0 elements. If you then run gst-inspect-1.0 vaapi you still get 0 elements, which isn't quite right. Perhaps we should add DISPLAY and whatever env var is used for wayland as plugin dependency so the plugin gets reloaded whenever it changes?
Created attachment 334601 [details] [review] vaapi: DISPLAY envvar as dependency In a multiple video cards system, a X11 environment may have different VA capabilities. This patch tracks the DISPLAY environment variable to invalidates the GStreamer features cache. Also tracks WAYLAND_DISPLAY.
Hi, the problem does not seem to happen in gst-uninstalled setup. I wanted it to check if it would be useful to add DRI_PRIME env var to that list too. This is how I am switching between integrated intel gpu and discrete nvidia gpu (gallium / nouveau). Isn't any gst-inspect option to force reloading a plugin to help debugging ?
Comment on attachment 334601 [details] [review] vaapi: DISPLAY envvar as dependency Thanks, was meaning to do the same :)
Attachment 334601 [details] pushed as 59821a2 - vaapi: DISPLAY envvar as dependency