- From: Cyril Concolato <cyril.concolato@telecom-paristech.fr>
- Date: Mon, 29 Sep 2014 18:14:19 +0200
- To: "public-inbandtracks@w3.org" <public-inbandtracks@w3.org>
Hi Kilroy, I think discussion on this bug should happen either in the bug or on the mailing list: public-inbandtracks@w3.org Now if I understood you, I think I agree and I raised that point in the following bug: https://www.w3.org/Bugs/Public/show_bug.cgi?id=26925 Regards, Cyril Le 29/09/2014 17:56, Kilroy Hughes a écrit : > I recommend identifying ISO/IEC 14496-30 (MPEG-4 Part 30) Subtitle tracks, in addition to audio and video. > > " For AdaptationSets for which the MIME Type is supported, it shall expose AdaptationSet whose MIME type is "video/*" (resp. "audio/*" or " application/ttml+xml") as HTML VideoTracks (resp. Audio or subtitle Tracks) and as TextTracks for all others." > > Both WebVTT and TTML (optionally, with images) can be delivered as a track in an ISO Media file or as DASH Media Segments containing ISOBMFF movie fragments. > A WebVTT IANA Media Type should be registered and included in order to recognize compatible WebVTT content and decoding capability. > > Kilroy Hughes | Senior Digital Media Architect |Windows Azure Media Services | Microsoft Corporation > > > -----Original Message----- > From: bugzilla@jessica.w3.org [mailto:bugzilla@jessica.w3.org] > Sent: Monday, September 29, 2014 2:02 AM > To: public-html-admin@w3.org > Subject: [Bug 26923] New: [InbandTracks] Number of HTML tracks from DASH > > https://www.w3.org/Bugs/Public/show_bug.cgi?id=26923 > > Bug ID: 26923 > Summary: [InbandTracks] Number of HTML tracks from DASH > Product: HTML WG > Version: unspecified > Hardware: PC > OS: Windows NT > Status: NEW > Severity: normal > Priority: P2 > Component: Sourcing In-band Media Resource Tracks > Assignee: silviapfeiffer1@gmail.com > Reporter: cyril.concolato@telecom-paristech.fr > QA Contact: public-html-bugzilla@w3.org > CC: mike@w3.org, public-html-admin@w3.org > > "A user agent recognises and supports data from a MPEG DASH media resource as being equivalent to a HTML track based on the AdaptationSet or ContentComponent mimeType:" > It is unclear how many tracks should be created: 1 per AS or 1 per Representation, or 1 per ContentComponent. Also, it is not clear which AS should be exposed ? All including those for which the mime type is not supported? > > Please rephrase using normative statements such as: > "User agents shall expose HTML tracks for all AdaptationSet elements in an MPD. > For AdaptationSets for which the MIME type is not supported, it shall expose the associated tracks as HTML TextTracks. For AdaptationSets for which the MIME Type is supported, it shall expose AdaptationSet whose MIME main type is "video" (resp. "audio") as HTML VideoTracks (resp. AudioTracks) and as TextTracks for all others. In a given AdaptationSet, UA shall expose all Representations as an HTML Track. If representations carry multiplexed streams, the UA shall expose each ContentComponent as an HTML Track." > > -- > You are receiving this mail because: > You are on the CC list for the bug. > -- Cyril Concolato Multimedia Group / Telecom ParisTech http://concolato.wp.mines-telecom.fr/ @cconcolato
Received on Monday, 29 September 2014 16:14:48 UTC