3 ms·
> I made this set of gifs of the same animation at different frame rates in ascending order(fps gets progressively higher). If any of them take a different amou
by Dylan16807 4y ago
> I made this set of gifs of the same animation at different frame rates in ascending order(fps gets progressively higher). If any of them take a different amount of time to reach the start and end points(they are all exactly 1 second long) then you know what framerate your browser is “restricting” the frame delay at.
"1 second long" is pretty misleading, especially when telling people to look for different amounts of time to render. None of the gifs from 8-30fps are properly trying to be a second long.
If you have software that assigns the same delay to each frame, that's a flaw you need to compensate for or switch to different software, and the author did neither.
Let's use the 30fps gif as an example. It runs 11% too fast. Either it should be rendered with 33 frames, making it run 1% too fast, or it should use frame timings of 30ms 30ms 40ms 30ms 30ms 40ms making it exactly 1 second total.
- Filligree 4y agoThe latter would cause a great deal of jitter. Not to mention, 40ms is 1.5 frame on a 60Hz display, so it isn't going to be 40ms anyway.
- kllrnohj 4y agoSince ~every web browser is vsync'd, most of these have jitter. The 50fps gif isn't 50fps, for example, as the browser never runs at 50fps itself.
- Dylan16807 4y agoYour math is off. 30ms is 1.8 frames and 40ms is 2.4 frames. Constant 30ms will jitter all by itself, and if anything 30 30 40 should reduce jitter or even eliminate it.