- From: Mark Callow <callow.mark@artspark.co.jp>
- Date: Thu, 20 Dec 2012 17:27:38 +0900
- To: Ian Hickson <ian@hixie.ch>
- Cc: whatwg@whatwg.org, Jer Noble <jer.noble@apple.com>
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
<http://randomascii.wordpress.com/2012/02/13/dont-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.
Regards
-Mark
--
注意：この電子メールには、株式会社エイチアイの機密情報が含まれている場合
が有ります。正式なメール受信者では無い場合はメール複製、 再配信または情
報の使用を固く禁じております。エラー、手違いでこのメールを受け取られまし
たら削除を行い配信者にご連絡をお願いいたし ます.
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.
Received on Thursday, 20 December 2012 08:29:00 UTC