Re: [webrtc-stats] TimingInfo metrics (#704)

Philip, it's per frame, but it's not available on all the frames.
So if we can add it as optional, requestVideoFrameCallback looks like a
better option.

The current way of reporting this metric is that because at the time it was
implemented, there were no per-frame callbacks.

On Fri, Oct 7, 2022 at 3:07 PM Philipp Hancke ***@***.***>
wrote:

> if we want to get this into the stats mdoel we need to do it differently
> since this is a per-frame thing which fits something like
> requestVideoFrameCallback much better?
>
> I tried some of this in
> https://chromium-review.googlesource.com/c/chromium/src/+/2675937 but
> then didn't find time to finish.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/webrtc-stats/issues/704#issuecomment-1271569217>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AF74EI6QPNRJASCULEFXCQTWCAOAFANCNFSM6AAAAAAQ7P4LKU>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>


-- 
Best regards,
Ilya


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


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 7 October 2022 13:09:18 UTC