W3C home > Mailing lists > Public > public-device-apis@w3.org > March 2010

RE: CaptureAPI initial comments

From: Tran, Dzung D <dzung.d.tran@intel.com>
Date: Wed, 24 Mar 2010 09:42:21 -0700
To: Rik Sagar <org.whatwg@sagar.org>, "public-device-apis@w3.org" <public-device-apis@w3.org>
Message-ID: <753F67ADE6F5094C9F1DBA00D1BAA8D325509DE786@orsmsx501.amr.corp.intel.com>
> A mime-type like video/mp4 is not sufficient detail for some formats.  You must take into account the combination of container/file-format and CODECs.  For example, a video captured in "MP4" could use one of several profiles (baseline, main, standard) and .mp4 doesn't tell you which.

Yes, you are right. This only specifies containter type and not necessary the CODECs. Many people associate container to as what the video format is just because commonly MP4 comes with H264/AAC. 


> CAPTURE IMAGE CALLBACKS
>
> The captureImage() call takes callbacks for success and error.  In a camera API I implemented recently I went with the event listener model, i.e., camera..addEventListener('save', callback, bubble);
> This is more consistent with the audio/video playback APIs (HTMLMediaElement) in HTML5 (and lots of other Javascript development these days).

We will look at this again. Thanks for the suggestion.

Regards,
Dzung Tran
Received on Wednesday, 24 March 2010 16:42:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:07 GMT