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

Re: Tech Discussions on the Multitrack Media (issue-152)

From: Philip Jägenstedt <philipj@opera.com>
Date: Wed, 02 Mar 2011 08:58:23 +0100
To: public-html@w3.org
Message-ID: <op.vrphrlzdsr6mfa@localhost.localdomain>
On Tue, 01 Mar 2011 23:51:30 +0100, David Singer <singer@apple.com> wrote:

> Hi Silvia, friends
>
> Eric and I have been discussing this, and we've added an 8th option to  
> the Wiki, for your consideration.
>
> at <http://www.w3.org/WAI/PF/HTML/wiki/Media_Multitrack_Media_API>

This is like option 2 except that <track> is not a void element and can  
have <source> child elements, right?

For all of the options that don't use <audio> and <video> to represent  
audio and video tracks, do you consider it a problem that properties of  
HTMLMediaElement are not available? Some of these allow for interesting  
conflicts such as looping a slave video but not the master video, but I  
imagine at least videoWidth, videoHeight and volume would be useful to  
have.

About multiple text track formats, my working assumption is that we will  
be able to agree on a single format that everyone supports as there is not  
really any of the legal of business issues that we have for audio and  
video.

If, however, we should both fail at finding a baseline text format and  
decide that we should use <track> for audio and video as well, then  
wouldn't multiple <track> elements with a type parameter be enough? We  
could define it such that multiple <track> elements that differ only in  
type should be assumed to representing the same content and have some kind  
of track selection algorithm for picking one. Am I too optimistic?

-- 
Philip Jägenstedt
Core Developer
Opera Software
Received on Wednesday, 2 March 2011 07:58:59 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:23 UTC