validate: allow config to check for minimum buffer frequency on pads
authorGuillaume Desmottes <guillaume.desmottes@collabora.com>
Thu, 7 Feb 2019 14:36:41 +0000 (15:36 +0100)
committerGuillaume Desmottes <guillaume.desmottes@collabora.com>
Wed, 20 Feb 2019 11:12:46 +0000 (12:12 +0100)
commitb20f73099f8a0221cd56acbab818ecf64a3bbb76
tree40d82226334e6bf15b2e43629c3c4e2e0925d2bd
parent40f263e85782620b0fba34061316ce24e89344ba
validate: allow config to check for minimum buffer frequency on pads

This change allow tests to check performance of elements by checking the
frequency at which buffers are pushed on src pads.
I re-used most of the logic from fpsdisplaysink to compute the
frequency.

We can now uses something like:
  GST_VALIDATE_CONFIG='core,min-buffer-frequency=60,target-element-factory-name=v4l2src'

The 'buffer-frequency-start' optional field can be used to ignore the
frequency during the start of the pipeline. This is useful when testing live
pipelines where configuring and setting up elements can take some time slowing
down the first buffers.
validate/docs/validate/envvariables.xml
validate/gst/validate/gst-validate-pad-monitor.c
validate/gst/validate/gst-validate-pad-monitor.h
validate/gst/validate/gst-validate-report.c
validate/gst/validate/gst-validate-report.h