Editing Talk:2628: Motion Blur

<!--Please sign your posts with ~~~~ and don't delete this text. New comments should be added at the bottom.-->
Personally, I'm animated on twos but make up for it with good smear frames. [[Special:Contributions/172.70.135.98|172.70.135.98]] 14:07, 4 June 2022 (UTC)

Can someone explain why it's been retitled to motion beans and the image has been replaced? Not sure if it's vandalism or a joke I don't understand. [[Special:Contributions/162.158.2.215|162.158.2.215]] 23:46, 4 June 2022 (UTC)
:vandalism [[Special:Contributions/172.70.206.163|172.70.206.163]] 23:54, 4 June 2022 (UTC)
::Is there anything that can be done about that? (Sorry not experienced with wiki rules/conventions). Looking that their history they have done quite a bit of vandalism in the past. [[Special:Contributions/162.158.2.219|162.158.2.219]] 00:36, 5 June 2022 (UTC)
:::As we have a good community, looking out for such things and resolving them, I don't think there's much extra we need to do but what we already do. I'm not giving credit to our interloper, but their actions have shown how we are clearly capable of stepping up to counter-action as required. Which is good.
:::Additional admin tool-use might be a further thing being lookedvat, but that's above my pay-grade to comment on. I think the current set of active Admins have done Ok and seem to have good heads on their shoulders, though, so happy to leave them to work those bits out too. [[Special:Contributions/172.70.162.5|172.70.162.5]] 09:35, 5 June 2022 (UTC)

== Randall has got this issue backwards: == 
Too *low* a framerate causes choppiness when panning (or on objects in motion). ''Too low'' a framerate causes the human eye to perceive multiple images of a mouse cursor; a higher framerate can exceed the perceptual latency of human vision, causing the moving cursor to be perceived as a continuous blur, whereas a lower framerate merely exacerbates the issue of seeing the cursor jump from position to position. 

To that point, the current explanation exemplifies this confusion, also getting it backward: ''"If the shutter speed is too high, this blurring will not occur, and the motion will look unnaturally crisp – if something is too small and/or too quick, the illusion of motion may disappear altogether; the object instead will appear as a brief flash of multiple objects standing still,"~'' '''This is incorrect.''' Human visual blur is ''not'' dependent on the displayed frames being blurred: With panning in high framerate video, unblurred footage ''appears blurred'' to the human eye, due to persistence of vision; whereas with low framerate video we may ''not'' perceive blurred motion & instead view each frame individually & perceive it as choppy. 

Point being, you need a framerate ''at least as high as 60 FPS'' to avoid choppy appearance when panning, & for some people's vision the minimum framerate to ensure motion blur is 100 FPS. 24 FPS is used in cinema ''to preserve the choppy look of old 24 FPS film projection'', as an aesthetic choice. 

Higher framerates look ''less'' choppy. ''Low'' framerates are what appears choppy when viewed. 
[[User:ProphetZarquon|ProphetZarquon]] ([[User talk:ProphetZarquon|talk]]) 14:10, 4 June 2022 (UTC)

:Yes, at high framerates, ''when the subject is perfectly sharp'', the blurring is done by human vision. At lower framerates, this natural blurring is mostly lost, and this effect must be counteracted by correspondingly lower shutter speeds so that motion appears blurry again. That's the whole point of the comic. [[User:Kapostamas|Kapostamas]] ([[User talk:Kapostamas|talk]]) 14:30, 4 June 2022 (UTC)

:: Exactly. Film typically has 24 FPS, animation is typically produced at 12 FPS, and 8 FPS is common in anime, and to make up for it by introducing the illusion of motion in other ways. With physical cameras that usually means low(ish) shutter speed to creating in-camera motion blur. [[Special:Contributions/172.70.134.95|172.70.134.95]] 20:00, 4 June 2022 (UTC)

In order to explain this, and prove that the explanation is correct (or prove that Randall is either correct or incorrect), there needs to be a link to two videos showing the error and the corrected version without the error. In other words, citation needed. [[Special:Contributions/172.70.126.65|172.70.126.65]] 15:35, 4 June 2022 (UTC)

:How's this: [https://youtu.be/i9bv00ZA-ao]? [[User:Kapostamas|Kapostamas]] ([[User talk:Kapostamas|talk]]) 16:47, 4 June 2022 (UTC)

::His shutter speed is ok, his FPS is too low :-). BTW, the worst thing done to anime is when some idiot decides to raise the framerate by inserting frames computed by averaging previous and following frame pixel by pixel ignoring the movement. -- [[User:Hkmaly|Hkmaly]] ([[User talk:Hkmaly|talk]]) 00:52, 5 June 2022 (UTC)
:::A number of years back, when TV weather maps were revamped with new computer graphics, it amused me when (e.g.) a couple of bands ('ripples') of cloud/rain were sometimes passing over bits of the national map, and while clearly the idea was that each was moving, the setup had the hindemost fading out (as an interpolated transition) while a new 'front' band fading in, the central one (in reality where the front one was in one predictive 'key frame' but coincidentally where the rear one had arrived to at the time-stamp of the next key-frame.
:::It probably needed the right weather-system transit speed (and feature-depth/separation) but something like this seemed to be common enough to do this or 'cinematic wagon-wheel' effects.
:::I think they must have revamped the presentation since, either more imported ksy-frames or imported "wind clues" to the interpolator... [[Special:Contributions/172.70.162.5|172.70.162.5]] 09:35, 5 June 2022 (UTC)