[whatwg] <video> feedback
callow.mark at artspark.co.jp
Thu Dec 20 00:27:38 PST 2012
On 2012/12/18 9:01, Ian Hickson wrote:
> On Tue, 2 Oct 2012, Jer Noble wrote:
>> The nature of floating point math makes precise frame navigation
>> difficult, if not impossible. Rob's test is especially hairy, given
>> that each frame has a timing bound of [startTime, endTime), and his test
>> attempts to navigate directly to the startTime of a given frame, a value
>> which gives approximately zero room for error.
> That makes sense.
> Should we add a preciseSeek() method with two arguments that does a seek
> using the given rational time?
I draw your attention to "Don't Store that in a float
and its suggestion to use a double starting at 2^32 to avoid the issue
around precision changing with magnitude as the time increases.
NOTE: This electronic mail message may contain confidential and
privileged information from HI Corporation. If you are not the intended
recipient, any disclosure, photocopying, distribution or use of the
contents of the received information is prohibited. If you have received
this e-mail in error, please notify the sender immediately and
permanently delete this message and all related copies.
More information about the whatwg