1. 26 Oct, 2018 1 commit
  2. 22 Oct, 2018 2 commits
    • Edward Hervey's avatar
      multiqueue: Don't clamp running times for position calculation · 127e2110
      Edward Hervey authored
      Since we use full signed running times, we no longer need to clamp
      the buffer time.
      
      This avoids having the position of single queues not advancing for
      buffers that are out of segment and never waking up non-linked
      streams (resulting in an apparent "deadlock").
      127e2110
    • Edward Hervey's avatar
      queue2: Reset result flow when retrying · 98fabd2f
      Edward Hervey authored
      If we ever get a GST_FLOW_EOS from downstream, we might retry
      pushing new data. But if pushing that data doesn't return a
      GstFlowReturn (such as pushing events), we would end up returning
      the previous GstFlowReturn (i.e. EOS).
      
      Not properly resetting it would cause cases where queue2 would
      stop pushing on the first GstEvent stored (even if there is more
      data contained within).
      98fabd2f
  3. 12 Sep, 2018 1 commit
  4. 31 Aug, 2018 2 commits
  5. 29 Aug, 2018 1 commit
  6. 28 Aug, 2018 1 commit
  7. 17 Aug, 2018 2 commits
  8. 16 Aug, 2018 1 commit
  9. 14 Aug, 2018 1 commit
  10. 01 Aug, 2018 2 commits
  11. 25 Jul, 2018 1 commit
  12. 24 Jul, 2018 1 commit
  13. 19 Jun, 2018 1 commit
  14. 04 Jun, 2018 1 commit
  15. 05 May, 2018 1 commit
  16. 01 May, 2018 1 commit
  17. 24 Apr, 2018 1 commit
  18. 17 Apr, 2018 2 commits
  19. 02 Mar, 2018 1 commit
  20. 01 Mar, 2018 1 commit
  21. 16 Feb, 2018 1 commit
  22. 24 Dec, 2017 2 commits
  23. 21 Dec, 2017 1 commit
  24. 14 Dec, 2017 1 commit
  25. 26 Nov, 2017 1 commit
  26. 24 Nov, 2017 2 commits
  27. 23 Nov, 2017 1 commit
  28. 10 Nov, 2017 1 commit
    • Edward Hervey's avatar
      concat: Handle single-pad use-cases · f03443f9
      Edward Hervey authored
      When EOS reaches concat, it will switch to the next candidate as its
      activate pad.
      
      The problem arises when there is only one sinkpad, the "active" pad
      becomes NULL. This results in concat becoming unusable after it receives
      a *single* EOS on its single sinkpad.
      
      If we detect there is a single sinkpad and there is no current active pad:
      * If we are waiting (from selected sink event/buffer), become the current
        active pad.
      * If there is a seek request, send it upstream. We don't switch the
        active_sinkpad property at that point in time, since the seek could
        fail. If the seek succeeds, the following SEGMENT (or STREAM_START)
        will cause the pad_wait() to elect that pad as the new active one.
      * Flush events get forwarded
      
      https://bugzilla.gnome.org/show_bug.cgi?id=790167
      f03443f9
  29. 09 Nov, 2017 1 commit
  30. 04 Nov, 2017 1 commit
  31. 02 Nov, 2017 1 commit
  32. 30 Oct, 2017 1 commit
    • Nicolas Dufresne's avatar
      latency-tracer: Exclude synchronization time · 41e35c33
      Nicolas Dufresne authored
      The goal of this tracer is to measure the processing latency between a
      src and a sink. In push mode, the time was read after the chain function
      have returned. As the amount of time we wait to get synched is reverse
      to the amount of latency the source introduced, the result was quite
      surprising.
      
      This patch moves the latency calculation in the pre-push hook. When
      there is no processing in a a pipeline (e.g. fakesrc ! fakesink), the
      latency will now be 0 as it's supposed to. For pull mode, the code was
      already correct. When GstBaseSink operate in pull mode, the processing
      time is done durring the pull, so pull-post is the right hook. The
      synchronization will happen after the pull has ended. Note that
      GstBaseSink rarely operate in pull mode.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=788431
      41e35c33
  33. 03 Oct, 2017 1 commit