GNOME Bugzilla – Bug 775041
vaapidecodebin: bring back dynamic configuration
Last modified: 2016-12-01 12:01:06 UTC
In commit ca0c3fd6 we remove the dynamic configuration if the bin because we assumed that the bin will be always static as it is registered. Nonetheless we were wrong, because it is possible to request, with a property, to avoid the use of the post-processor. Since we want to add a way to disable the post-processor through environment variables, this remove feature is required again. If the environment variable GST_VAAPI_DISABLE_VPP is defined the postprocessor inside of the vaapidecodebin is disabled, then vaapidecodebin is an alias of the old vaapidecode.
Created attachment 340706 [details] [review] vaapidecodebin: bring back dynamic configuration
Comment on attachment 340706 [details] [review] vaapidecodebin: bring back dynamic configuration commit 4609f7fd5e35fef9699578e2e7c104a143a2f896 Author: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com> Date: Mon Nov 21 19:29:22 2016 +0100 vaapidecodebin: bring back dynamic configuration In commit ca0c3fd6 we remove the dynamic configuration if the bin because we assumed that the bin will be always static as it is registered. Nonetheless we were wrong, because it is possible to request, with a property, to avoid the use of the post-processor. Since we want to add a way to disable the post-processor through environment variables, this remove feature is required again. If the environment variable GST_VAAPI_DISABLE_VPP is defined the postprocessor inside of the vaapidecodebin is disabled, then vaapidecodebin is an alias of the old vaapidecode. https://bugzilla.gnome.org/show_bug.cgi?id=775041