1. 29 Aug, 2017 1 commit
  2. 14 Aug, 2017 2 commits
  3. 09 Jul, 2017 1 commit
  4. 02 Jun, 2017 1 commit
  5. 01 Jun, 2017 1 commit
    • Tim-Philipp Müller's avatar
      rtph264depay: simplify buffer accumulation control flow · a68a7fb6
      Tim-Philipp Müller authored
      There is no difference between pushing out a buffer directly
      with gst_rtp_base_depayload_push() and returning it from the
      process function. The base class will just call _depayload_push()
      on the returned buffer as well.
      
      So instead of marshalling buffers through three layers and back,
      just push them from one place in handle_nal() and always return
      NULL from the process vfunc. This simplifies the code a little.
      
      Also rename _push_fragmentation_unit() to _finish_fragmentation_unit()
      for clarity. Push sounds like it means being pushed out, whereas
      it might just be pushed into an adapter.
      
      This change has the side-effect that multiple NALs in a single STAP
      (such as SPS/PPS) may no longer be pushed out as a single buffer if
      we output NALs in byte-stream format (i.e. not aggregate AUs), but
      that shouldn't really make any difference to anyone.
      a68a7fb6
  6. 24 May, 2017 3 commits
  7. 16 May, 2017 1 commit
  8. 24 Apr, 2017 1 commit
  9. 16 Mar, 2017 1 commit
  10. 10 Mar, 2017 1 commit
  11. 28 Feb, 2017 2 commits
  12. 27 Feb, 2017 3 commits
  13. 20 Feb, 2017 1 commit
  14. 23 Jan, 2017 1 commit
  15. 09 Jan, 2017 1 commit
  16. 18 Dec, 2016 1 commit
  17. 13 Dec, 2016 1 commit
  18. 01 Dec, 2016 1 commit
  19. 28 Nov, 2016 1 commit
  20. 01 Nov, 2016 5 commits
  21. 27 Sep, 2016 1 commit
  22. 24 Sep, 2016 1 commit
    • Arun Raghavan's avatar
      rtpsbcpay: Fix timestamping · 10a16a63
      Arun Raghavan authored
      We were just picking the timestamp of the last buffer pushed into our
      adapter before we had enough data to push out.
      
      This fixes things to figure out how large each frame is and what
      duration it covers, so we can set both the timestamp and duration
      correctly.
      
      Also adds some DISCONT handling.
      10a16a63
  23. 15 Sep, 2016 1 commit
  24. 14 Sep, 2016 2 commits
  25. 06 Sep, 2016 1 commit
  26. 26 Aug, 2016 4 commits