W3C home > Mailing lists > Public > public-media-capture-logs@w3.org > January 2017

Re: [mediacapture-record] Reconsider isTypeSupported() API

From: ddorwin via GitHub <sysbot+gh@w3.org>
Date: Tue, 31 Jan 2017 20:46:57 +0000
To: public-media-capture-logs@w3.org
Message-ID: <issue_comment.created-276486887-1485895616-sysbot+gh@w3.org>
I think the more important question is how we expect applications to 
use the API. In what cases would an application call either of these 
APIs and why? In most cases, it seems that the ability for the same 
user agent to play a codec might be sufficient. (Should their be 
guidance/requirements in the spec related to this?) Perhaps an 
application wants to request a more optimal codec, a codec that is 
better supported by the backend, or 10-bit - all when available.

Once the intended use is understood, you can look at ways to 
accomplish it, such as specifying maximums or ranges in requests to 
create a recorder. Would getUserMedia's constraints model be 
applicable?

-- 
GitHub Notification of comment by ddorwin
Please view or discuss this issue at 
https://github.com/w3c/mediacapture-record/issues/93#issuecomment-276486887
 using your GitHub account
Received on Tuesday, 31 January 2017 20:47:03 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:27:31 UTC