W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > March 2019

Re: [mediacapture-main] Why do we have overconstrained event? (#573)

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Sat, 23 Mar 2019 09:44:51 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-475855769-1553334290-sysbot+gh@w3.org>
@fluffy Yes you are right that this can happen, but I think we are trying to use constraints for different problems/use cases at the same time.

"Did I get what I asked for?" is actual two questions.
1. Is the track constrained the way I asked it? This means, is it configured with settings that are compatible with my constraints. I.e. it is configured with the right resolution? Is it configured to produce the framrate I asked for?
2. Is the source able to produce what it is configured to produce?

Note that 1) is the only thing that browser/constraints processing and thus application has any control over. And the answer to 1) is always Yes. The answer to 2) is probably always yes except for things like framerate, which could drop due to lighting conditions, CPU usage, etc.

Let's not confuse _constraints processing and device configurations_ with _device/network diagnostics_. The source could be local, or remote, whatever. Conditions may vary, frames may drop, this is separate from whether or not things are configured properly. They are configured correctly, so "overconstrained" is misleading, and often times not actionable. Add to the fact that as defined it also mutes your track it's a total foot-gun, though that could be amended without removing it altogether.

A drop in framerate would have you ask "was it temporary? was it continuous?". How long do you wait until you give up on the device? This is totally use case and application-specific. Simplifying this problem to "am I overconstrained or not?" (forget "how/why am I overconstrained?") I would argue is not in anybody's best interest if alternatives are considered.

I don't think fixing this or considering alternatives should block "1.0". If need for something like this manifests itself stronger it would be better served addressed separately.

GitHub Notification of comment by henbos
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/573#issuecomment-475855769 using your GitHub account
Received on Saturday, 23 March 2019 09:44:52 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:46 UTC