1. 02 Nov, 2015 1 commit
  2. 26 Feb, 2015 1 commit
  3. 11 Feb, 2015 1 commit
  4. 17 Nov, 2014 1 commit
  5. 03 Nov, 2014 1 commit
  6. 01 Oct, 2014 3 commits
  7. 24 Sep, 2014 1 commit
  8. 04 Sep, 2014 1 commit
  9. 14 Aug, 2014 2 commits
  10. 08 Aug, 2014 1 commit
  11. 04 Jul, 2014 1 commit
    • Tim-Philipp Müller's avatar
      videomixer: fix double unlock in segment seek segment code path · deeef84d
      Tim-Philipp Müller authored
      We only want to unlock if we push an event downstream and
      jump to done_unlock label afterwards. We would also unlock
      in case of a segment seek and then unlock again later, and
      nothing good can come of that.
      
      (This code looks a bit dodgy anyway though, shouldn't it
      also bail out with FLOW_EOS here in case of a segment seek
      scenario, just without the event?)
      deeef84d
  12. 01 Jul, 2014 1 commit
  13. 26 Jun, 2014 1 commit
  14. 25 Jun, 2014 1 commit
  15. 16 Apr, 2014 4 commits
  16. 16 Mar, 2014 1 commit
  17. 11 Mar, 2014 1 commit
  18. 27 Nov, 2013 1 commit
  19. 22 Nov, 2013 1 commit
  20. 04 Oct, 2013 1 commit
  21. 11 Sep, 2013 1 commit
  22. 10 Sep, 2013 3 commits
  23. 04 Sep, 2013 1 commit
  24. 24 Aug, 2013 1 commit
  25. 17 Aug, 2013 1 commit
  26. 11 Aug, 2013 1 commit
  27. 06 Aug, 2013 1 commit
  28. 21 Jul, 2013 1 commit
    • Mathieu Duponchelle's avatar
      videomixer: use gst_util_uint64_scale*_round. · d67a671b
      Mathieu Duponchelle authored
      There could be a case where:
            1) you do a new set_caps after buffers have been processed.
            2) ts_offset gets set to a different value, eg 0.033333333
            3) your pads get EOS, but the check dor that doesn't work
               because you use ts_offset + a truncated value < segment.stop
            4) so in the next collected, you end up comparing for example:
            0.9999999999 > 1., which is false and means you don't send EOS.
      
      Also adds scale_round in two other places where it potentially could
      have caused problems.
      d67a671b
  29. 09 Jul, 2013 2 commits
  30. 12 Jun, 2013 1 commit
  31. 11 Jun, 2013 1 commit