OK, so googAvgEncodeMs is measured starting from a frame entering the encoder and stopping after packetization, over a sliding window. For a standardized version of this stat I think it makes more sense to start and stop the clock around the encoding of each frame, this is more straight-forward and clear what it means. -- GitHub Notification of comment by henbos Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/150#issuecomment-282042481 using your GitHub accountReceived on Thursday, 23 February 2017 16:25:30 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:40 UTC