W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2011

[whatwg] Stream API Feedback

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Tue, 15 Mar 2011 11:23:57 +0100
Message-ID: <4D7F3E3D.4030200@lachy.id.au>
On 2011-03-14 17:59, Lachlan Hunt wrote:
> There are a few issues with the recently added media streaming API.

In addition to what I sent previously, there are some additional use 
cases that do not appear to be addressed adequately by the current spec 
for streaming media.

In chat clients, like Skype, it's common for users to be able to adjust 
the microphone volume or mute the audio stream, or to enable or disable 
the video stream, without interupting the call.  However, the 
GeneratedStream interface only provides a very simple API to pause, 
resume or stop the entire stream, and not individual tracks within the 
stream.

e.g.

var stream;
navigator.getUserMedia("audio,video", success);

function success(s) {
   stream = s;
   // ... Code to make P2P connection for video chat
}

In this case, stream.pause() will pause both the audio and video 
streams, whereas the user, for example, may just temporarily want to 
pause the video stream, leaving the audio enabled.

While it may be possible for the browser to allow such control entirely 
from the browser chrome, independently of the page, the page author may 
wish to provide customised controls for these features.  I believe the 
API should be adjusted to allow the individual tracks within a stream to 
be paused or resumed independently of each other, and for there to be 
some way to adjust or mute the microphone volume.

-- 
Lachlan Hunt - Opera Software
http://lachy.id.au/
http://www.opera.com/
Received on Tuesday, 15 March 2011 03:23:57 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:31 UTC