Re: [webrtc-stats] RTCCodecStats needs `transportId` and `isRemote` to give it context

You're right, "encode-only"/"decode-only"/"encode-decode" is better 
than "isRemote", since it would be redundant to have two identical 
codecs with only an "isRemote" bit flipped.

I think it would be nice to have the ability to use the codec stats in
 this way; for example, to see what codecs a PeerConnection is 
*prepared* to receive, even if not actively receiving.

-- 
GitHub Notification of comment by taylor-b
Please view or discuss this issue at 
https://github.com/w3c/webrtc-stats/issues/109#issuecomment-267661844 
using your GitHub account

Received on Friday, 16 December 2016 18:24:56 UTC