Difference between revisions of "Media Capture"

From W3C Wiki
Jump to: navigation, search
Line 5: Line 5:
== Documents ==
== Documents ==
The [http://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/scenarios.html scenario/req draft], and the [http://dev.w3.org/2011/webrtc/editor/getusermedia.html API draft]. Both are currently Editor's drafts.
The [http://dvcs.w3.org/hg/dap/raw-file/tip/media-stream-capture/scenarios.html scenario/req draft], the [http://dev.w3.org/2011/webrtc/editor/getusermedia.html API draft] and the [http://lists.w3.org/Archives/Public/public-media-capture/2012Dec/att-0159/RecordingProposal.html Recording].
== Meetings ==
== Meetings ==

Revision as of 10:37, 18 January 2013

The Media Capture API (a.k.a. navigator.getUserMedia) is developed by a joint task force between the WebRTC and Device APIs Working Groups (see the task force charter).

This page serves as a coordination point for the work in this task force.


The scenario/req draft, the API draft and the Recording.


First telco took place on Feb 9th, 5.00 - 6.30pm CET. Minutes: http://lists.w3.org/Archives/Public/public-media-capture/2012Feb/att-0021/minutes-2012-02-09.html

Second Telco took place on Feb 28th, 5.00 - 6.30pm CET. Minutes: http://lists.w3.org/Archives/Public/public-media-capture/2012Feb/att-0049/minutes-2012-02-28.html

Third Telco took place on April 24th, 10.00 - 11.30pm CET. Minutes: http://lists.w3.org/Archives/Public/public-media-capture/2012Apr/att-0031/minutes-2012-04-24.html

Fourth Telco took place on May 9th, 10.00 - 11.30pm CET. Minutes: http://lists.w3.org/Archives/Public/public-media-capture/2012May/0070.html

Fifth Telco took place June 7th, 5.00 - 6.30pm CET. Minutes: http://lists.w3.org/Archives/Public/public-media-capture/2012Jun/0055.html

Sixth Telco: Aug 23rd. Minutes: http://lists.w3.org/Archives/Public/public-media-capture/2012Aug/0149.html

Next telco scheduled for Oct 9th, 10.00 - 11.30pm CET.

F2f meeting scheduled for Oct 30 2012

Useful resources

Mailing lists


  • Tracker is used to track actions within the group. We're only using the ACTION section.
  • Buganizer, the "Media Capture and Streams" component, is available for tracking issues and bugs.


The group uses IRC to take minutes and exchange info during calls and face-to-face meetings:

Open Items

Note: just a first brain dump; has not been discussed or agreed in any way.//Stefan 2012-04-24

Simple image capture API

iFrame behavior

Direct assignment of MediaStream to Video

Possibility to from JS create a dummy track and add to a MediaStream

  • dummy track can be used to insert DTMF in (to enable using IVR without access to mic or cam)

Possibility to select sources other than cam or mic

  • we need the possibility to use other sources than the actual device to getUserMedia so that users can fake the access to a camera
  • there is also another need: the webrtc reqs mandate that the screen should be a valid source (to enable screen sharing)

Enable display of level in Audio tracks

Enable adjustment of audio level

Possibility to change streams without doing getUserMedia

Closed Items

Change getUserMedia to force error handling

Direct assignment of MediaStream to Canvas

Integration of MediaStream with media elements

How to deal with several active devices

Resource reservation