- From: henbos via GitHub <sysbot+gh@w3.org>
- Date: Thu, 21 Jun 2018 10:32:24 +0000
- To: public-webrtc-logs@w3.org
henbos has just created a new issue for https://github.com/w3c/webrtc-stats: == Input/output resolution and audio energy == The resokution, audio level, etc. values for sender/receiver/track stats are not clear which part of the pipeline they apply to, see discussions at #271. The sender is really encoder + packetizer: https://photos.app.goo.gl/fyqGKxYMhM247dK47 The same is true for receiver but in reverse order. We should consider splitting this up sender/receiver into encoder / decoder dictionaries references by the sender/receiver and put the metrics there. Whether we put them there or keep them inside the sender/receiver/track dictionaries, any frame/audio metrics need to have both "inputBlah" and "outputBlah" versions. Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/353 using your GitHub account
Received on Thursday, 21 June 2018 10:32:34 UTC