1. 24 Feb, 2019 2 commits
    • Thibault Saunier's avatar
      validate: Notice that issue summaries should be 'stable' · c7270b2d
      Thibault Saunier authored
      As they are used in the testsuite to define known issues
      c7270b2d
    • Alicia Boya García's avatar
      gst-validate-scenario: Make waits optional in appsrc-push · f0abd316
      Alicia Boya García authored
      While in many cases it's desirable to wait for a buffer to be pushed
      downstream when using appsrc-push, in some cases this is not possible as
      such pushing action is dependent on following actions that would not be
      executed if we wait.
      
      An example for this is prerolling:
      
          appsrc ! qtdemux ! video/x-h264 ! decodebin name=dec ! %(videosink)s
      
          description, seek=false, handles-states=true
          appsrc-push, target-element-name=appsrc0, file-name="raw_h264.0.mp4"
          set-state, state=playing
          appsrc-eos, target-element-name=appsrc0
      
      In order for the preroll to occur, both the appsrc needs to push the
      buffer and the state needs to reach PLAYING. But `set-state` cannot
      finish if the buffer has not been pushed (the state transition does not
      finish) and conversely pushing the buffer will not finish until the
      state has reached.
      
      Making appsrc-push not wait for the buffer solves this problem. This
      patch makes appsrc-push aware of this issue by only waiting for the
      buffer to be pushed if the pipeline is in a state that allows buffers to
      flow.
      f0abd316
  2. 21 Feb, 2019 2 commits
  3. 20 Feb, 2019 2 commits
    • Guillaume Desmottes's avatar
      validate: allow config to check for minimum buffer frequency on pads · b20f7309
      Guillaume Desmottes authored
      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.
      b20f7309
    • Guillaume Desmottes's avatar
  4. 18 Feb, 2019 1 commit
  5. 15 Feb, 2019 7 commits
  6. 12 Feb, 2019 1 commit
  7. 11 Feb, 2019 4 commits
  8. 10 Feb, 2019 1 commit
  9. 09 Feb, 2019 3 commits
  10. 08 Feb, 2019 3 commits
  11. 07 Feb, 2019 3 commits
  12. 06 Feb, 2019 2 commits
  13. 02 Feb, 2019 1 commit
  14. 01 Feb, 2019 8 commits