summaryrefslogtreecommitdiff
path: root/gst/vaapi/gstvaapiencode_h265.c
diff options
context:
space:
mode:
authorVíctor Manuel Jáquez Leal <victorx.jaquez@intel.com>2015-11-11 19:04:25 +0100
committerVíctor Manuel Jáquez Leal <victorx.jaquez@intel.com>2015-11-16 16:07:07 +0100
commitbd4395ce9f2bf037a86cd9597b4b22b652e61e8c (patch)
tree2e3cbfacb6e48933eaf516aefa8ee98c2f7c269d /gst/vaapi/gstvaapiencode_h265.c
parentce3d1a6203330d6a2110797dc89709605c4c9282 (diff)
downloadgstreamer-vaapi-bd4395ce9f2bf037a86cd9597b4b22b652e61e8c.tar.gz
vaapidecodebin: add postprocessor dynamically
The former approach to left the bin unfinished has some problems: the context cannot be shared because the vaapidecode is unlinked in many cases, leading to creating a VADisplay twice. Initially the bin is fully functional, constructed as (-----------------------------------) | vaapidecodebin | | (-------------) (-------) | |<--| vaapidecode |--->| queue |--->| | (-------------) (-------) | (-----------------------------------) When the context is shared and the VADisplay has VPP capabilities, before changing to READY state, the bin is reconfigured dynamically, adding the vaapipostproc element afeter the queue: (--------------------------------------------------------) | vaapidecodebin | | (-------------) (-------) (---------------) | |<--| vaapidecode |--->| queue |--->| vaapipostproc |--->| | (-------------) (-------) (---------------) | (--------------------------------------------------------) Signed-off-by: Víctor Manuel Jáquez Leal <victorx.jaquez@intel.com> https://bugzilla.gnome.org/show_bug.cgi?id=757957
Diffstat (limited to 'gst/vaapi/gstvaapiencode_h265.c')
0 files changed, 0 insertions, 0 deletions