- From: <bugzilla@jessica.w3.org>
- Date: Mon, 05 Aug 2013 12:13:57 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22785 --- Comment #15 from Silvia Pfeiffer <silviapfeiffer1@gmail.com> --- (In reply to comment #8) > (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. For something like this to work, we'd need to define a new @kind of text track that has this expected behavior - namely to switch between media tracks. I think given the work on Web Animations, we may not even need need the use of a WebVTT track to pre-schedule transitions between different video tracks - Web Animations should be capable of providing that functionality: http://dev.w3.org/fxtf/web-animations/ together with the use of track fragments to specify which track to switch to: http://www.w3.org/TR/2011/CR-media-frags-20111201/#naming-track . -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 5 August 2013 12:13:59 UTC