W3C home > Mailing lists > Public > www-style@w3.org > September 2012

Re: [css3-transitions] Frame Rate

From: Jon Rimmer <jon.rimmer@gmail.com>
Date: Thu, 27 Sep 2012 13:39:37 +1000
Message-ID: <CA+ZDCiB+x+3h26V8xPUy2seF8D6GRzHZ6uj4bKp4kGS+2SC21w@mail.gmail.com>
To: François REMY <fremycompany_pub@yahoo.fr>
Cc: David Singer <singer@apple.com>, Martijn Korteweg <martijn@mediaartslab.com>, "www-style@w3.org" <www-style@w3.org>
On 15 September 2012 04:31, François REMY <fremycompany_pub@yahoo.fr> wrote:
> I think Sylvain got it: it's to simulate low end hardware on high end
> hardware (ie: making sure the anim is acceptable and the jigger isn't too
> awful).
>

I don't think it is. I strongly suspect this is about working with
animators who are creating content in traditional animation tools,
like Flash or ToonBoom, who work at a traditional framerate of 24p
[1]. If/when their animations are converted to CSS, the browser will
play it at as high a framerate as possible, interpolating between the
keyframes. This can result in a different "feel" to the fluidity of
the animation, which will be particularly noticable to the animators
who spent many hours working on it. You could argue this is a workflow
issue, and they should switch to animating at 60fps, but some may be
resistant to this, especially if they are deliberately trying to
recreate the feel of traditional film and broadcast animation.

It's worth noting that audiences can notice these things as well. The
ability of different framerates to add or subtract to an experience
has recently been in the news due to Peter Jackson's decision to film
and show the film The Hobbit in both 24fps and 48fps [2]. Some
audience members reponded quite negatively to preview footage of the
48fps version.

[1] http://en.wikipedia.org/wiki/24p
[2] http://www.engadget.com/2012/05/28/editorial-48-fps-hobbit-preview-high-frame-rates/

Jon Rimmer
Received on Thursday, 27 September 2012 03:40:05 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:00 GMT