[Bug 24859] Automatic Video and Audio Track Selection Based on User Preferences and Terminal Characteristics

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24859

Jon Piesing (HbbTV) <hbbtvjon@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hbbtvjon@gmail.com

--- Comment #2 from Jon Piesing (HbbTV) <hbbtvjon@gmail.com> ---
>I don't think any of what you are asking for is "excluded" in the HTML spec. In fact, some of it is explicitly mentioned.

That's great to hear but the text quoted in the issue suggests the opposite. If
that's wrong then it should be fixed.

>For example, the spec encourages user agents to expose a user interface of some sort (e.g. a menu or a remote control) through which viewers can select between different available audio and video tracks for a video in
http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#expose-a-user-interface-to-the-user
.

This issue isn't about user input while the content is presenting but about
user preferences set before the content starts being presented, perhaps even
when the user was watching broadcast TV via a different part of the TV set.

>Re Use Case 1:
How are you delivering "clean audio" tracks and "audio tracks with audio
descriptions" to TV receivers through the <object> tag in a way that they are
uniquely identifiable right now?

Clean audio and audio description (etc) are signalled as part of the media
resource and then acted on by the media player in the TV by default. With the
object element, we have our own JavaScript API for media playback using the
object element that pre-dates the HTML5 video element. This exposes more
metadata about all types of track than the HTML5 media elements (see #24863). 

>Re Use Case 2:
I don't understand what you are asking for. I assume you're asking if the user
agent according to the HTML spec can auto-activate specific audio and video
tracks based on user preferences and terminal characteristics? If so, the
answer is: yes, absolutely.

That's great news but as I said above, the text quoted in the issue suggests
the opposite. If that's wrong then it should be fixed.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Sunday, 2 March 2014 11:08:14 UTC