- From: Sean DuBois via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Jun 2020 21:00:23 +0000
- To: public-webrtc-logs@w3.org
@guidou thanks for the help! So I am trying to send into Chromium for another agent. Do you know what I need to implement as a minimum to get this working? I am not using libwebrtc at all, so need to figure out stuff at the protocol level. ---- @murillo128 So I don't fully understand how this all ties together, here are my naive questions :) * This API is just giving access to the RTP Payloads? * Why does it need to be codec aware? If I just want to do a simple XOR across all the bytes on each side, does it matter? * How/why do those RTP extension headers come into play? Is there more logic then just handling the SSRC/PayloadType? I haven't had a chance to fully grok sframe yet, I assumed `Insertable Streams` was just a matter of giving a callback to users so they could flip bytes around in the Payload. -- GitHub Notification of comment by Sean-Der Please view or discuss this issue at https://github.com/w3c/webrtc-insertable-streams/issues/37#issuecomment-643481134 using your GitHub account
Received on Friday, 12 June 2020 21:00:24 UTC