W3C home > Mailing lists > Public > public-web-perf@w3.org > February 2013

[RequestAnimationFrame] ally: Separate capture & display cycles

From: Jonathan Chetwynd <jay@peepo.com>
Date: Mon, 11 Feb 2013 12:37:49 +0000
Message-ID: <5118E61D.2050605@peepo.com>
To: public-web-perf@w3.org
 From the perspective of display, and human vision there is a reasonable 
argument for limiting display updates to 60fps.

However from a data capture perspective this is totally mistaken.
Cameras including the 2007 PS3 eye camera offer speeds of 125fps and faster.
Children and researchers need a simple means to access this data.

use cases range from a study of horses galloping, or butterfly wings,
where data may be displayed, at a slower speed than captured, at a later 

to eye tracking solutions that use frame rates in the range 30-1300fps
to process images and estimate accelerations, vectors, and locations.

Browser based solutions offer opportunities for improving accessibility, 
whilst broadening participation and developing understanding.

For this reason I propose that RAF should not be throttled to 60fps, and 
that the display cycle be a separate process.

kind regards

Jonathan Chetwynd
Eyetracking in HTML5
Received on Monday, 11 February 2013 12:38:15 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:34 UTC