incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Braden Shepherdson (JIRA)" <>
Subject [jira] [Commented] (CB-1052) Media API does not adhere to whitelist
Date Mon, 17 Sep 2012 15:29:07 GMT


Braden Shepherdson commented on CB-1052:

Okay, I've done a bunch of reading. This is a very volatile area. It looks like WebRTC's getUserMedia()
is the standard way forward for recording audio. For playing audio, there's the (complex and
much more powerful than our Media) Web Audio API, which is actually pretty impressive. It
allows filter effects and building a graph of sources, filters and destinations similarly
to PulseAudio on Linux. It supports precise realtime mixing and synthesizing, as well.

For our purposes, both APIs are overkill. Polyfilling them fully would be hard, since we're
a long way from eg. writing full mixer support on our various platforms. A more basic polyfill
would be filled with caveats, as many parts of the standard API would be unsupported.

I think the best approach here would be to leave our Media API in place for now, and eventually
port it to use the standard API under the hood on platforms that support it (currently none
to my knowledge).

That doesn't address the whitelist question, of course.
> Media API does not adhere to whitelist
> --------------------------------------
>                 Key: CB-1052
>                 URL:
>             Project: Apache Cordova
>          Issue Type: Bug
>          Components: Android
>    Affects Versions: 1.9.0
>            Reporter: Filip Maj
>            Assignee: Simon MacDonald
>            Priority: Critical
>             Fix For: 2.2.0
> You can see this in the mobile-spec test (where it by default tests media using an external
> Shouldn't it adhere to the whitelist?
> Setting to minor priority and not slating for any specific release.
> -- Posted from Bugbox for Android

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message