Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RTCMediaStreamTrackStats.keyFramesReceived #234

Closed
henbos opened this issue Aug 15, 2017 · 2 comments
Closed

RTCMediaStreamTrackStats.keyFramesReceived #234

henbos opened this issue Aug 15, 2017 · 2 comments
Assignees

Comments

@henbos
Copy link
Collaborator

henbos commented Aug 15, 2017

We have RTCMediaStreamTrackStats.framesReceived which is the count of frames including both key frames and non-key frames.

I propose we add RTCMediaStreamTrackStats.keyFramesReceived which is a counter for only the portion of received frames that are key frames. (Non-key frames = framesReceived - keyFramesReceived.)

@henbos
Copy link
Collaborator Author

henbos commented Aug 15, 2017

The number of key frames can have a large impact on performance, network pacing and other flow mechanism as well as CPU and media quality. It should be useful for diagnosing and be clear how to implement cross browsers.

@henbos henbos self-assigned this Aug 30, 2017
@vr000m
Copy link
Contributor

vr000m commented Aug 30, 2017

keyFramesSent and keyFramesReceived makes sense. what do we do about partial key frames? probably this triggers a FIR (fullIntraFrameRequest)? or what does the receiver do then?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants