Signaling in WebRTC

แชร์
ฝัง

ความคิดเห็น • 8

  • @addanametocontinue
    @addanametocontinue 9 หลายเดือนก่อน

    Interesting. I'm working on a demo app and was running into errors because my impression was that the signaling is a symmetrical process between both peers. Based on the diagrams shown here, it is not. There is an initiator of the connection and a receiver and both parties do things differently depending on which role they play. Thanks for the pictures, that really helps.

  • @tuancharlie1
    @tuancharlie1 5 ปีที่แล้ว

    Hi, thanks for the great vid
    !
    Using Chrome and Opera on some mobile devices the image gets compressed vertically, no matter if using constraints or not on the getUserMedia or if sizing the video tag, while always fine in mobile Firefox, and all desktop browsers. Any clue or direction to debug? Many thanks, cheers, Mat

  • @StephenMoreira
    @StephenMoreira 4 ปีที่แล้ว

    Thanks for the content!

  • @justphanithings2019
    @justphanithings2019 4 ปีที่แล้ว

    Is it a good idea to have one way communication through sdp? like one client broadcasting to other client without receiving anything.

    • @can9
      @can9 4 ปีที่แล้ว +1

      Yes, in your situation, you need to make one client send only and other client receive only. WebRTC can be used to "one to many", "one to one" or" n to many" broadcasting. But if you target large viewers, you need a media server which will replicate broadcaster's sdp to viewers. So every participant will make just one connection with server. You can use open source project Janus for this. (Video Room Plugin and Streaming Plugin)

    • @hirisraharjo
      @hirisraharjo 3 ปีที่แล้ว

      @@can9 When you say large, how large?

    • @can9
      @can9 3 ปีที่แล้ว +1

      @@hirisraharjo It depends on client's bandwidth. Usually when you target 6+ people in a session, you need yo implement media server with MCU or SFU methods. Because, mesh system will cause high bandwidth usage on clients.

    • @hirisraharjo
      @hirisraharjo 3 ปีที่แล้ว +1

      @@can9 thanks!