1,295
edits
MediaStreamAPI: Difference between revisions
→Streams, RTC, audio API and media controllers
| Line 1: | Line 1: | ||
= Streams, RTC, audio API and media controllers = | = Streams, RTC, audio API and media controllers = | ||
The ideas here build on [http://www.whatwg.org/specs/web-apps/current-work/complete/video-conferencing-and-peer-to-peer-communication.html Ian Hickson's WhatWG proposal], adding features partly inspired by [https://wiki.mozilla.org/Audio_Data_API the Mozilla audio API] and [http://chromium.googlecode.com/svn/trunk/samples/audio/specification/specification.html the Chrome audio API]. Unlike previous proposals | The ideas here build on [http://www.whatwg.org/specs/web-apps/current-work/complete/video-conferencing-and-peer-to-peer-communication.html Ian Hickson's WhatWG proposal], adding features partly inspired by [https://wiki.mozilla.org/Audio_Data_API the Mozilla audio API] and [http://chromium.googlecode.com/svn/trunk/samples/audio/specification/specification.html the Chrome audio API]. Unlike previous audio API proposals, the API presented here integrates with proposed API for media capture from local devices, integrates with proposed API for peer-to-peer media streaming, handles audio and video in a unified framework, incorporates Worker-based Javascript audio processing, and specifies synchronization across multiple media sources and effects. The API presented here does not include a library of "native" effects; those can be added as a clean extension to StreamProcessor, perhaps as a "level 2" spec. | ||
=== Scenarios === | === Scenarios === | ||