- From: Nigel Megitt via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Jun 2018 14:18:22 +0000
- To: public-web-and-tv@w3.org
Thinking more about https://github.com/w3c/media-and-entertainment/issues/4#issuecomment-397593999 : > transferring the playback state (e.g. currentTime) from player to JS takes more than 0 time, the value received in JS will always be outdated. Can this not be modelled or measured adaptively though to minimise the impact? > Triggering events with event handlers at 50hz will make increase resource usage by a lot, even if there is no real reason for it. @Snarkdoof have you got data to back this up? Running _time marches on_ when the list of events to add to the queue is empty is not going to take many CPU clock cycles. Relative to the resource needed to play back video, I suspect it is tiny. But the advantage of doing it is huge when there is an event to add to the queue. It'd be good to move from speculation (on both our parts!) to measurement. -- GitHub Notification of comment by nigelmegitt Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/4#issuecomment-397635627 using your GitHub account
Received on Friday, 15 June 2018 14:18:24 UTC