- From: Snarkdoof via GitHub <sysbot+gh@w3.org>
- Date: Mon, 18 Jun 2018 18:32:38 +0000
- To: public-web-and-tv@w3.org
@nigelmegitt @tidoust - I guess I just never understood the whole time marches on algorithm to be honest, it seems like a very strange way to wait for a timeout to happen, in particular when the time to wait can be very reliably be calculated well in advance. The added benefit of doing this properly in JS is that the flexibility is excellent - there is no looping anywhere, there is an event after a setTimeout, re-calculated when some other event is triggered (skip, pause, play etc). We use it for all kinds of things - showing subtitles, switching between sources, altering css, preloading images at a fixed time, etc. Preloading is trivial if you give a sequencer a time shifted timing object. Say you need up to 9 seconds to prepare an image - time shift it to 10 seconds more than the playback clock and do nothing else! I might of course be absolutely in the black on the Time marches on, text and data cues (I did test them, and found them horrible a couple of years ago). But the only thing I crave is the timestamp on the event - it will solve our every need (almost) and at barely any cost. :) -- GitHub Notification of comment by Snarkdoof Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/4#issuecomment-398152041 using your GitHub account
Received on Monday, 18 June 2018 18:32:51 UTC