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

Re: ISSUE-85 (codecs): No provisions for audio/x-speex, video/x-webm, audio/ogg, or video/ogg [Capture API]

From: Rik Sagar <org.whatwg@sagar.org>
Date: Wed, 9 Jun 2010 11:18:57 -0700
Message-ID: <AANLkTilYvrQ43LMvKbatZS_VRRS1ySebrlOHmkASMJcl@mail.gmail.com>
To: Device APIs and Policy Working Group WG <public-device-apis@w3.org>
Could the additional information be expressed in the codec attribute?

Actually, there's a similar issue with JPEG images.  You can, when creating
a JPEG, specify a "QUALITY" for the encoding.  How does the capture API
allow that to be specified?

Rik.





On Wed, Jun 9, 2010 at 5:30 AM, Device APIs and Policy Working Group Issue
Tracker <sysbot+tracker@w3.org <sysbot%2Btracker@w3.org>> wrote:

>
> ISSUE-85 (codecs): No provisions for audio/x-speex, video/x-webm,
> audio/ogg, or video/ogg [Capture API]
>
> http://www.w3.org/2009/dap/track/issues/85
>
> Raised by: James Salsman
> On product: Capture API
>
> MIME types audio/x-speex, video/x-webm, audio/ogg, and video/ogg should all
> be referred to.
>
> Speex has a variable bitrate, customarily expressed as a value from 0 to
> 10, in addition to a choice of three sampling rates.  Both parameters need
> to be exposed in the API.  Please see
> http://en.wikipedia.org/wiki/Speex#Features and
> http://www.speex.org/comparison/ for more information.
>
> It is not appropriate to refer to audio/wav, a Microsoft-defined union type
> with dozens of possible instances (WAVE RIFF union type format) only some of
> which are open, only some of which meet contemporary quality and performance
> standards, and some of which are ambiguous.
>
>
>
>
>
>
Received on Wednesday, 9 June 2010 18:19:51 GMT

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