W3C home > Mailing lists > Public > public-media-capture@w3.org > March 2013

Re: Updated Media Capture and Streams editor's draft

From: Dan Burnett <dburnett@voxeo.com>
Date: Mon, 25 Mar 2013 09:09:16 -0400
Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-Id: <ECD1F6FD-5A76-4FAE-A66B-BA6901544CCC@voxeo.com>
To: "Mandyam, Giridhar" <mandyam@quicinc.com>
Quick replies on a few items below to avoid misunderstandings.

On Mar 25, 2013, at 12:29 AM, Mandyam, Giridhar wrote:

> Great stuff.  I apologize in advance for mixing questions related to historical features in the spec versus new changes.
> 
> 1.  Section 4.1.  "A MediaStream object is said to be finished when all tracks ... have ended."  Should the corresponding state attribute be called  "finished" instead of "ended"?
> 
> 2.  Section 4.2.2.  Why do the getVideoTracks/getAudioTracks methods return sequences instead of MediaStreamTrackArrays?
> 
> 3. Section 4.3.2.  appendConstraint, prependConstraint methods.  I assume that these methods preserve the relative priority of previous optional constraints, while making the new constraint highest priority if it is prepended and lowest if it is appended.  Is this correct?  If so, it should probably be clarified in this section.
> 
> 4.  Section 4.3.2.  Do developers really need all these methods?  In short, wouldn't it be possible to manipulate constraints through the applyConstraints() method and nothing else?
> 
> 5. Section 4.3.3.  In the Image Capture proposal I put forward, there is a getFrame() method that provides frame capture in the form of an RGBA byteArray.  Is it possible to execute such a method on both a 'camera' and a 'photo-camera'?   If not, why not?
> 
> 6. Section 4.3.2.  Example in the "NOTE" section refers to constraints (e.g. fillLightMode) that are not listed in the IANA registry (Section 10.1).  

I had copied this almost verbatim from Travis' document.  I meant to adjust to match the demo list of constraints in section 10.1.  I will adjust in the next draft.

> 
> 7. Section 10.1.  This is missing two constraints that I thought the group was OK with - zoom and fillLightMode. 

As I mentioned in the large note preceding that section, this is not intended to be the "approved" list.  You may also have noticed that "aspectRatio" was not included, although it was more popular in the straw poll at the interim than zoom and fillLightMode.  Again, this is just a sample set so we can talk intelligently with concrete examples.

> 
> -Giri
> 
> -----Original Message-----
> From: Dan Burnett [mailto:dburnett@voxeo.com] 
> Sent: Wednesday, March 20, 2013 10:56 AM
> To: public-media-capture@w3.org
> Subject: Updated Media Capture and Streams editor's draft
> 
> Hi
> 
> A new version of the editor's draft is available.
> 
> Dated version: http://dev.w3.org/2011/webrtc/editor/archives/20130320/getusermedia.html
> Living document: http://dev.w3.org/2011/webrtc/editor/getusermedia.html
> 
> Changes include:
> * Changed error code to be string instead of number.
> * Added core of settings proposal allowing for constraint changes after stream/track creation.
> 
> Note that capabilities and source states will likely also be added at some point.  This version focuses on initial integration of constraint/setting changes.
> 
> 
> Please review and provide feedback.
> 
> Dan Burnett (for the editors)
> 
> 
> 
Received on Monday, 25 March 2013 13:09:47 UTC

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