Re: [webrtc-stats] RTCCodecStats.implementation... per-codec, per-stream?

The "implementation" is meaningless without knowing the codec, I 
think. We will also find that different implementations have different
 parameters (for instance, most Mac hardware H.264 codecs support HIgh
 Profile, which will be indicated in codec.parameters).

So it belongs with the codec stats, conceptually.
I'd create a codec stat for every used implementation, and make the 
RTCRTPStreamStats.codecId point to the corresponding codec stat as of 
the time of the call.

Moving it to streamStats might be easier, but doesn't pass the "smell 
test" for me.

GitHub Notification of comment by alvestrand
Please view or discuss this issue at 
using your GitHub account

Received on Monday, 30 January 2017 16:53:42 UTC