W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > June 2020

Re: [webrtc-insertable-streams] Does Chromium require anything in SDP or RTP Header to make this work? (#37)

From: Sergio Garcia Murillo via GitHub <sysbot+gh@w3.org>
Date: Sun, 14 Jun 2020 00:01:01 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-643696102-1592092860-sysbot+gh@w3.org>
> @murillo128 @guidou @SourceCodeZone @agouaillard Figured it out!
> It had nothing to do with anything discussed in the issue, this is just an issue in the browser. When using a XOR Cipher with a cipherKey of `0xAB` it causes video decode failures. If I use `0xAA` it works. My code from two days ago works I just need to change `0xAB` => `0xAA` 
> https://jsfiddle.net/zmwo640s/ In the JS try change `CIPHER_KEY` to `0xAB`. There is probably some rule to Javascript I am missing here.
> Also huge shout out to @murillo128 and @guidou, this has been one of the best interactions in Open Source I have had in a while. Thank you so much for taking your time to answer my questions (no matter how stupid they are). Hopefully stuff like this convinces others it is possible to have a community like that :)

You are not skipping the first 3 or 10 bytes of the vp8 frame, and as you are not using the generic paquetizer/descriptor that changes the vp8 descriptor which is used by chrome for packetization and everything is broken.

Changing from 0xAB to 0xAA probably just keep some bits intact after encryption that made it work just by pure luck.

GitHub Notification of comment by murillo128
Please view or discuss this issue at https://github.com/w3c/webrtc-insertable-streams/issues/37#issuecomment-643696102 using your GitHub account
Received on Sunday, 14 June 2020 00:01:03 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:51 UTC