- From: Jeroen Wijering <jeroen@jwplayer.com>
- Date: Mon, 19 Jan 2015 15:39:44 -0500
- To: Steve Heffernan <steve@zencoder.com>
- Cc: John Luther <jluther@jwplayer.com>, David Singer <singer@apple.com>, Philip Jägenstedt <philipj@opera.com>, "public-texttracks@w3.org" <public-texttracks@w3.org>, rick.eyre@hotmail.com, gkatsevman@brightcove.com
With JW Player, we implemented basic parsing of cues and rendering of cues according to the draft spec. Especially in the area of rendering, the spec is well defined and very helpful to implementors. With TTML and SRT, we had to be much more creative in doing the rendering. Let me know what exactly you'd like to see in terms of feedback on the spec; our player engineers can put that together. We have not yet implemented regions. It's a bit hard to comment on the spec without doing the work; you always find the small details when implementing. It reads very defined and focused to the use case though (608 compatibility). If you require comments from people that have implemented the spec, we could look into prioritizing this work for JW Player. The one item I'm missing from the spec is inline CSS, but that's pushed to V2 right? (https://www.w3.org/Bugs/Public/show_bug.cgi?id=15023) On platforms like Flash or native Android, we'd like to have all cue styling inline since there's no CSS. Publisher also need it when converting from legacy formats (608, TTML) into VTT. In these formats, the styling also "lives" inline. - Jeroen On Wed, Jan 14, 2015 at 4:40 PM, Steve Heffernan <steve@zencoder.com> wrote: > I've CC'd Gary Katsevman who's done the most work with the vtt spec for > Video.js. Gary, how do you feel about the state of the VTT spec? Did you run > into any issues that could be submitted as a bug? > > Also CC'd Rick Eyre (mozilla/vtt.js) though he's probably already on the > list. > > -Steve
Received on Tuesday, 20 January 2015 08:55:18 UTC