W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > August 2011

[Bug 13625] There is no way to pass audio and video content metadata to the user agent that is required in some cases for playback.

From: <bugzilla@jessica.w3.org>
Date: Thu, 11 Aug 2011 17:04:18 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QrYg6-0003H8-65@jessica.w3.org>

--- Comment #5 from Bob Lund <b.lund@cablelabs.com> 2011-08-11 17:04:16 UTC ---
(In reply to comment #4)
> http://www.whatwg.org/specs/web-apps/current-work/multipage/video-conferencing-and-peer-to-peer-communication.html#obtaining-local-multimedia-content
> getUserMedia has an options parameter which could probably be used to pass
> along whatever initialization data is needed.

Thanks for the link. It looks like getUserMedia is used to expose a local media
source while the use case stimulating this bug was the client accessing content
from a server. It seems however that the getUserMedia object could be applied
to the remote content use case in the following way:

- The options attribute would be used to convey the media URL that the local UA
uses to fetch the media.

- The options attribute would also be used to convey metadata specific to that
content that the local UA needs to correctly decode the content.

- Depending on the metadata, certain behavior of the MediaStream may be
disabled, recording for example or forking of specific tracks.

I am assuming that when using the MediaStream (returned by getUserMedia) as a
child of <video>, multiple video, audio and text tracks in the MediaStream
would be exposed per HTML5 support for multiple video/audio tracks and <track>.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 11 August 2011 17:04:19 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:02:00 UTC