plugins: avoid log flood when activating pool
authorVíctor Manuel Jáquez Leal <victorx.jaquez@intel.com>
Wed, 18 Jan 2017 16:20:21 +0000 (17:20 +0100)
committerVíctor Manuel Jáquez Leal <victorx.jaquez@intel.com>
Wed, 18 Jan 2017 16:25:44 +0000 (17:25 +0100)
commit7fd41c42639d0603015bf467d9fb8b1eef15c078
treef36aafb826c4da0c538a9ef97ea0a4b5508bc425
parent86548296280a4e3f640799faefed2cee073e33ec
plugins: avoid log flood when activating pool

Every time a new buffer is allocated, the pool is activated. This
doesn't impact in performance since gst_buffer_pool_set_active()
checks the current state of the pool. Nonetheless it logs out a
message if the state is the same, and it floods the logging subsystem
if it is enabled.

To avoid this log flooding first the pool state is checked before
changing it.
gst/vaapi/gstvaapipluginbase.c
gst/vaapi/gstvaapipostproc.c