W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2019

Re: [csswg-drafts] [css-animation] Motion Blur (#3837)

From: Surma via GitHub <sysbot+gh@w3.org>
Date: Thu, 25 Jul 2019 10:51:35 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-514997225-1564051894-sysbot+gh@w3.org>
One consideration I would like to add: Shutter angle alone will make the motion blur inherently frame rate dependent and therefore potentially device specific. We know that most devices run at 60fps, but there are some 90Hz, 120Hz or even 400Hz screens out there. Just defining a shutter angle and using the device’s native frame rate will yield drastically different visuals depending on the screen they are shown on.

Another side of the same coin: Motion blur is often used to achieve a certain aesthetic. For example, there is the concept of “cinematic” motion blur, which is what you get when you shoot a movie at ~25fps with a shutter angle of 180deg. That aesthetic is unachievable if you can’t define a target frame rate. 

I’d love for this proposal to somehow solve this. I am not sure if just defining a target “emulated” frame rate would be sufficient or if it would just make things look weirder. I do know that some modern digital cameras are able to shoot at 60fps and add “cinematic” motion blur as a post-processing step. I’d love to get some insight from someone with cinematography knowledge here.

-- 
GitHub Notification of comment by surma
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3837#issuecomment-514997225 using your GitHub account
Received on Thursday, 25 July 2019 10:51:36 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:50 UTC