1. 08 Oct, 2018 1 commit
    • Aleix Conchillo Flaqué's avatar
      webrtcbin: start and stop thread when changing state · c4fe5239
      Aleix Conchillo Flaqué authored
      It might be possible that if we set webrtcbin to the NULL state some
      tasks (idle sources) are still executed and they might even freeze. The freeze
      is caused because the webrtcbin tasks don't hold a reference to webrtcbin and
      if it's last unref inside the idle source itself this will not allow the main
      loop to finish because the main loop is waiting on the idle source to finish.
      
      We now start and stop webrtcbin thread when changing states. This will allow
      the idle sources to finish properly.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=797251
      c4fe5239
  2. 21 Sep, 2018 2 commits
  3. 19 Sep, 2018 1 commit
  4. 19 Jul, 2018 1 commit
  5. 15 Jul, 2018 1 commit
  6. 14 Jul, 2018 1 commit
  7. 12 Jul, 2018 1 commit
    • Mathieu Duponchelle's avatar
      find_codec_preferences: use received caps · 6fd3e2a4
      Mathieu Duponchelle authored
      When negotiation is triggered by receiving caps on our sink pad
      probes, we could encounter a race condition where need-negotiation
      is emitted and the application requires the creation of an offer
      before the current caps were actually updated.
      
      This led to retrieving incomplete caps when creating the offer,
      using find_codec_preferences -> pad_get_current_caps.
      
      Instead, as we save the caps in the probe callback anyway, it is better
      and thread safe to use these if they were set.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=796801
      6fd3e2a4
  8. 01 Jul, 2018 1 commit
  9. 23 Jun, 2018 1 commit
  10. 29 May, 2018 1 commit
  11. 28 May, 2018 1 commit
  12. 09 May, 2018 1 commit
  13. 16 Mar, 2018 1 commit
  14. 08 Feb, 2018 3 commits
  15. 02 Feb, 2018 1 commit
    • Matthew Waters's avatar
      webrtcbin: an element that handles the transport aspects of webrtc connections · 1894293d
      Matthew Waters authored
      SDP's are generated and consumed according to the W3C PeerConnection API
      available from https://www.w3.org/TR/webrtc/
      
      The SDP is either created initially from the connected
      sink pads/attached transceivers as in the case of generating an offer or
      intersected with the connected sink pads/attached transceivers as in
      the case for creating an answer.  In both cases, the rtp payloaded streams
      sent by the peer are exposed as separate src pads.
      
      The implementation supports trickle ICE, RTCP muxing, reduced size RTCP.
      
      With contributions from:
      Nirbheek Chauhan <nirbheek@centricular.com>
      Mathieu Duponchelle <mathieu@centricular.com>
      Edward Hervey <edward@centricular.com>
      
      https://bugzilla.gnome.org/show_bug.cgi?id=792523
      1894293d