1. 03 Apr, 2015 2 commits
  2. 02 Apr, 2015 6 commits
  3. 01 Apr, 2015 2 commits
  4. 30 Mar, 2015 2 commits
  5. 29 Mar, 2015 3 commits
  6. 28 Mar, 2015 4 commits
  7. 26 Mar, 2015 3 commits
  8. 25 Mar, 2015 2 commits
  9. 24 Mar, 2015 5 commits
  10. 23 Mar, 2015 1 commit
  11. 21 Mar, 2015 2 commits
    • Sebastian Dröge's avatar
      rtpsession: Fix another instance of sticky event misordering warnings · 0e3609a6
      Sebastian Dröge authored
      Make sure that the sync_src pad has caps before the segment event.
      Otherwise we might get a segment event before caps from the receive
      RTCP pad, and then later when receiving RTCP packets will set caps.
      This will results in a sticky event misordering warning
      
      This fixes warnings in the rtpaux unit test but also in the
      rtpaux and rtx examples in tests/examples/rtp
      
      https://bugzilla.gnome.org/show_bug.cgi?id=746445
      0e3609a6
    • Sebastian Dröge's avatar
      rtpsession: Also start the RTCP send thread when receiving RTP or RTCP · 17d90b45
      Sebastian Dröge authored
      Before we only started it when either:
      - there is no send RTP stream
      or
      - we received an RTP packet for sending
      
      This could mean that if the send RTP pads are connected but never receive any
      RTP data, and the same session is also used for receiving RTP/RTCP, we would
      never start the RTCP thread and would never send RTCP for the receiving part
      of the session.
      
      This can be reproduced with a pipeline like:
      
      gst-launch-1.0 rtpbin name=rtpbin \
      udpsrc port=5000 ! "application/x-rtp, media=video, clock-rate=90000, encoding-name=H264" ! rtpbin.recv_rtp_sink_0 \
      udpsrc port=5001 ! rtpbin.recv_rtcp_sink_0 \
      rtpbin.send_rtcp_src_0 ! fakesink name=rtcp_fakesink silent=false async=false sync=false \
      rtpbin.recv_rtp_src_0_2553225531_96 ! decodebin ! xvimagesink \
      fakesrc ! valve drop=true ! rtpbin.send_rtp_sink_0 \
      rtpbin.send_rtp_src_0 ! fakesink name=rtp_fakesink silent=false async=false sync=false -v
      
      Before this change the rtcp_fakesink would never send RTCP for the receiving
      part of the session (i.e. no receiver reports!), after the change it does.
      
      And before and after this change it would send RTCP for the receiving part of
      the session if the sender part was omitted (the last two lines).
      17d90b45
  12. 19 Mar, 2015 2 commits
  13. 18 Mar, 2015 1 commit
  14. 16 Mar, 2015 3 commits
  15. 15 Mar, 2015 1 commit
  16. 14 Mar, 2015 1 commit