- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Jul 2015 16:27:37 +0000
- To: public-media-capture-logs@w3.org
To me, this begs a lot of questions:
* `navigator.mediaDevices` has `getUserMedia()`, but no API yet for
addressing outputs AFAIK, so what will these Capabilities be used for?
* **Permission:** Why must I share my mic (or camera) with a
sound-producing site/game for it to access info about (not even actual
control-access to) speakers? That doesn't make any sense to me. Also,
if I don't have a camera or microphone, how can a site gain info
about my speakers/output-recording devices?
* **Constraints:** *Capabilities* is one third of the *Constrainable*
pattern (*Capabilities*/*Settings*/*Constraints*), yet there's no
Constrainable API for output devices, so is this reuse
non-constraints-related? Also, as @joeberkovitz points out,
*MediaTrack*Capabilities, are source capabilities, not sink
capabilities. Should we really reuse these for cross-purposes?
-
dictionary MediaTrackCapabilities {
(double or DoubleRange) volume;
(long or LongRange) sampleRate;
(long or LongRange) sampleSize;
sequence<boolean> echoCancellation;
(double or DoubleRange) latency;
(long or LongRange) channelCount;
DOMString deviceId;
DOMString groupId;
};
We're surely stretching definitions here.
--
GitHub Notif of comment by jan-ivar
See
https://github.com/w3c/mediacapture-main/pull/211#issuecomment-126007883
Received on Wednesday, 29 July 2015 16:27:38 UTC