W3C home > Mailing lists > Public > public-media-capture@w3.org > August 2016

[mediacapture-fromelement] define behaviors of the common ConstrainablePattern Interfaces

From: ShijunS via GitHub <sysbot+gh@w3.org>
Date: Tue, 23 Aug 2016 16:40:11 +0000
To: public-media-capture@w3.org
Message-ID: <issues.opened-172748257-1471970409-sysbot+gh@w3.org>
ShijunS has just created a new issue for 
https://github.com/w3c/mediacapture-fromelement:

== define behaviors of the common ConstrainablePattern Interfaces  ==
The spec currently doesn't cover behaviors for the 
ConstrainablePattern Interfaces.  As example, here are some questions 
with applyConstraints()
- Whether the "frameRate" constraint can be applied to video track 
captured from video element and canvas (might be relevant to issue 
#43)
- Whether apps want to capture a lower resolution video from an 
UHD/4k-video source, and whether the "width" and "height" constraints 
should be honored in that case
- Whether the "channelCount" constraint should be applied for captured
 audio tracks.  As an potential use case, we might need to convert 
multi-channel audio to stereo before we send it out with 
peerconnection.  
- How about other audio constraints: volume, sampleRate, and 
sampleSize - although it might require audio DSP operations so leading
 to more complexity in implementations.  

In case any of the common ConstrainablePattern Interfaces is 
irrelevant, the spec should call that out explicitly.

Please view or discuss this issue at 
https://github.com/w3c/mediacapture-fromelement/issues/48 using your 
GitHub account
Received on Tuesday, 23 August 2016 16:40:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:37 UTC