- From: Brendan Long <B.Long@cablelabs.com>
- Date: Wed, 14 May 2014 15:43:21 +0000
- To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, "Ladd, Pat" <Pat_Ladd2@cable.comcast.com>
- CC: "Clift, Graham" <Graham.Clift@am.sony.com>, Bob Lund <B.Lund@CableLabs.com>, "public-inbandtracks@w3.org" <public-inbandtracks@w3.org>
> > I am currently looking at how to generically map such things to > > DataCue, or whether we should use a new MPEG-based Cue format that > > Bob has been designing. There'll be more on this soon. > > I just want to clarify that CEA-608 and CEA-708 wouldn't make sense in Bob's > MPEG-TS cues. Those are for exposing MPEG-TS sections, but CEA-608 and > 708 are stored in the video stream, not at the container level, so their format > is completely different. .. but we could still easily render them, that's a separate issue. I'm just saying that if we want to expose CEA-708 to JavaScript, we'll need to map it to WebVTT, expose it as a DataCue, or create a CEA708Cue interface.
Received on Wednesday, 14 May 2014 15:43:53 UTC