- From: <bugzilla@jessica.w3.org>
- Date: Wed, 24 Jul 2013 17:51:21 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22785 --- Comment #8 from Aaron Colwell <acolwell@google.com> --- (In reply to comment #6) > On the other end, if you "describe" the ad brakes in a TextTrack, the player > could interpret it ahead of playback and do the switches without requiring > user scripts to do anything. Yes. My intent was that the cues "describe" the switches to the media engine. The expectation is that the application provides these descriptions "early enough" that the media engine can use them to provide seamless transitions. If the application tries to add a cue "too close" to the current playback position then there are very limited guarentees about how seamless the transition will be. This would provide some wiggle room for any sort of buffering & delays that may be present in the media engine or JavaScript engine. "Too close" is probably somewhere between 20-500ms depending on the media engine. > > events are still useful if the application wants to be notified of the ad > start/end, e.g. for analytics purposes. That was my thought as well. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 24 July 2013 17:51:22 UTC