- From: Byoungchan Lee via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Nov 2022 02:35:38 +0000
- To: public-webrtc-logs@w3.org
I think you are referring to the case with spatial scalability. I think the case of temporal scalability is fine. For example, consider L2T3 with an input case of 30 fps. [Image](https://w3c.github.io/webrtc-svc/#L2T3*) Each spatial layer consists of three temporal layers. TL0 is 7.5 fps, TL1 is 15 fps and TL3 is 30 fps. This results in an encoded frame with three different temporal layers that repeat: TL0 - TL2 - TL1 - TL2. In this case, all temporal layers should be counted when calculating frames. For spatial layers, I agree that they should report at 30 fps. In libwebrtc's code, `codec_info == nullptr || The codec_info->end_of_picture` condition ([link](https://source.chromium.org/chromium/chromium/src/+/main:third_party/webrtc/video/send_statistics_proxy.cc;drc=d81992197c9e31d9009a0c6ee9d3862479773c06;l=989)) would be enough, but I'm not sure how to write it in specification terms. (Probably something like this: `For SVC, it returns the total number of frames in the top active spatial layer.`) -- GitHub Notification of comment by bc-lee Please view or discuss this issue at https://github.com/w3c/webrtc-stats/issues/711#issuecomment-1331569911 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 November 2022 02:35:40 UTC