Skip to content
This repository has been archived by the owner on Feb 1, 2022. It is now read-only.

Remove depth map calibration parameters #168

Merged
merged 3 commits into from
Mar 1, 2019
Merged

Conversation

astojilj
Copy link
Contributor

@astojilj astojilj commented Feb 28, 2019

Implemented experiments [1] showed that:

  • Application could be responsible to provide the values based
    on camera name, with no need to obtain the values from hardware.
  • There is no standardized approach to obtain the calibration
    parameters, by browser from hardware.

This simplifies the specification and makes it in line with already
implemented (in Blink) videoKind property.

[1] https://github.com/01org/depth-camera-web-demo


Preview | Diff

Implemented experiments [1] showed that:
* Application could be responsible to provide the values based
  on camera name, with no need to obtain the values from hardware.
* There is no standardized approach to obtain the calibration
  parameters, by browser from hardware.

This simplifies the specification and makes it in line with already
implemented (in Blink) videoKind property.

[1] https://github.com/01org/depth-camera-web-demo
@astojilj
Copy link
Contributor Author

@anssiko
PTAL

index.src.html Show resolved Hide resolved
Copy link
Member

@anssiko anssiko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the following are not used in normative prose and can be dropped:

overconstrained
NavigatorUserMediaSuccessCallback
videoTrack
HTMLMediaElement
srcObject
CanvasImageSource
permission
"camera"
default value

@astojilj
Copy link
Contributor Author

astojilj commented Mar 1, 2019

Thanks. Removed them and MediaVideoElement and Float32Array, too - they were used in non-normative, code examples, only.

@anssiko
Copy link
Member

anssiko commented Mar 1, 2019

LGTM. Thanks!

@anssiko anssiko merged commit 36e4eb0 into w3c:gh-pages Mar 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants