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

Width/height as setting should be configured, not native. #909

Open
henbos opened this issue Oct 12, 2022 · 2 comments
Open

Width/height as setting should be configured, not native. #909

henbos opened this issue Oct 12, 2022 · 2 comments

Comments

@henbos
Copy link
Contributor

henbos commented Oct 12, 2022

Add similar clarifications as we did in https://github.com/w3c/mediacapture-main/pull/908/files but for width and height. For example the native camera resolution may be bigger than what we see due to scaling or cropping.

@jan-ivar
Copy link
Member

A camera may struggle to maintain a frame rate. Why would it struggle to maintain resolution?

I think apps expect {width, height} = track.getSettings() to reflect actual dimensions.

@jan-ivar
Copy link
Member

Oh I think I see, the language on frame rate deals with 3 things, the configured setting, vs. the native setting, vs. the measured setting.

For resolution, you'd like language on 2 things, the configured setting, vs. the native setting? If I understand correctly that makes sense to me.

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