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

Clarify that frameRate as a setting is the configured value, not a measurement. #908

Merged
merged 2 commits into from
Oct 13, 2022

Conversation

henbos
Copy link
Contributor

@henbos henbos commented Oct 12, 2022

Fixes #906.


Preview | Diff

@henbos
Copy link
Contributor Author

henbos commented Oct 12, 2022

This is what we expect to see under ideal conditions, which may or may not be what we measure.

getusermedia.html Outdated Show resolved Hide resolved
getusermedia.html Show resolved Hide resolved
@jan-ivar
Copy link
Member

How is this different from #512?

@henbos
Copy link
Contributor Author

henbos commented Oct 13, 2022

How is this different from #512?

I don't think it's different, it's just a clarification. Not only does Chrome implement to "sometimes return a setting and sometime return a measurement" but it turns out this misunderstanding has even spread to more recent specs written after that clarification was added:
https://w3c.github.io/mediacapture-transform/#generator-constrainable-properties

So being explicit about it seems like a good thing

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

Successfully merging this pull request may close these issues.

MediaStreamTrack.getSettings().frameRate should reflect configured rate, not actual
4 participants