W3C home > Mailing lists > Public > public-web-and-tv@w3.org > June 2018

Re: [media-and-entertainment] Frame accurate seeking of HTML5 MediaElement

From: Snarkdoof via GitHub <sysbot+gh@w3.org>
Date: Fri, 15 Jun 2018 11:34:20 +0000
To: public-web-and-tv@w3.org
Message-ID: <issue_comment.created-397593999-1529062459-sysbot+gh@w3.org>
In comment to @nigelmegitt [1] increase the timeupdate to 50hz, I'd just like to point out two things:
1. As 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. We see this very clearly as massive jitter in the currentTime reporting. Going to 50hz will make this error smaller, but it will still be there.

2. Triggering events with event handlers at 50hz will make increase resource usage by a lot, even if there is no real reason for it. For example, updating a progress bar at 50hz is just silly, similarly, a subtitle that is shown for 5.4 seconds will have executed the code for checking if it should be removed 269 times for no reason.

A 

[1] https://github.com/w3c/media-and-entertainment/issues/4#issuecomment-397209849

-- 
GitHub Notification of comment by Snarkdoof
Please view or discuss this issue at https://github.com/w3c/media-and-entertainment/issues/4#issuecomment-397593999 using your GitHub account
Received on Friday, 15 June 2018 11:34:22 UTC

This archive was generated by hypermail 2.3.1 : Friday, 15 June 2018 11:34:23 UTC