Skip to content
Permalink
Browse files

Updated to allow RTX to be negotiated for h264 since this seems fixed…

… in Chrome now. (#640)
  • Loading branch information...
stefhak authored and stefanalund committed Sep 20, 2016
1 parent c997bff commit 439b9431cfdba86a311b1cf850b464b349285f3a
Showing with 2 additions and 4 deletions.
  1. +2 −4 bridge/client/webrtc.js
@@ -53,12 +53,10 @@
],
"video": [
{ "encodingName": "H264", "type": 103, "clockRate": 90000,
"ccmfir": true, "nackpli": true, "ericscream": true, /* "nack": true, */
"ccmfir": true, "nackpli": true, "ericscream": true, "nack": true,
"parameters": { "levelAsymmetryAllowed": 1, "packetizationMode": 1 } },
/* It turns our Chrome still does not handle RTX for h264 correctly, so making
it not be negotiated
{ "encodingName": "RTX", "type": 123, "clockRate": 90000,
"parameters": { "apt": 103, "rtxTime": 200 } }, */
"parameters": { "apt": 103, "rtxTime": 200 } },
{ "encodingName": "VP8", "type": 100, "clockRate": 90000,
"ccmfir": true, "nackpli": true, "nack": true, "ericscream": true },
{ "encodingName": "RTX", "type": 120, "clockRate": 90000,

0 comments on commit 439b943

Please sign in to comment.
You can’t perform that action at this time.