- From: <bugzilla@jessica.w3.org>
- Date: Mon, 17 Mar 2014 16:10:56 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24997 --- Comment #6 from Bob Lund <b.lund@cablelabs.com> --- (In reply to Silvia Pfeiffer from comment #5) > I have prepared a patch for this in a branch at > https://github.com/w3c/html/commit/f91c1932220ab4272d2b2b4e6c9f3679251fefa1 . > > Could you please check that this is all correct, in particular for MPEG-2, > MPEG-4 and DASH (I checked Ogg and WebM and am quite confident on those). For MPEG-4 metadata text track, you've used a list of sample entry codes instead of 'meta' handler type. Beyond, 'mett' and 'metx', I do not know if this list is accurate or not. The table for setting text track kind, label and language looks good. > > Further: > > * In bug 25044 you're requesting some similar specifications for setting the > id, label and language on AudioTrack and VideoTrack. Is that identical to > the TextTrack settings for these attributes? Yes, the rules for setting id, label and language should apply to audio and video as well as text tracks. > > * Please particularly check the @kind settings for MPEG-2, MPEG-4 and DASH. > MPEG-2 and MPEG-4 sound particularly restrictive, e.g. there is no fallback > to @kind=metadata. For MPEG-2 TS there are many many non-audio/video stream types beyond those explicitly identified as metadata (0x05, 0x80 - 0xff), with no identified use case for exposing them to script. For MPEG-4, it seems that all metadata tracks would be identified by a handler type of 'meta'. Is there a use case where that is not so? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 17 March 2014 16:10:58 UTC