[quote]"mairo":/users/38571 said: Hz is basically how many times your monitor refreshes, where FPS is how many frames are shown, but yeah, many use these interchangeabely because how closely tied together these are in real use. [/quote] I mean, Hz isn't specifically how many times the monitor refreshes. Hz is just "per second" basically, so it measures how many times something happens per second. The amount of time in between each wave period? Hz. How many times a monitor can change the frame it shows? Hz. How many times a frame is changed? Hz. All FPS is Hz, but not all Hz is FPS. But yeah, FPS is the amount of frames shown per second. In this video's case, it's 60 frames per second, but was likely originally rendered at 48 frames per second (which can still be represented with Hz, but Hz is more of an umbrella unit that can represent multiple things, fps included)

Hot femboys always drive me batty; love this!!!

[quote]"jmvryt":/users/560267 said: Every 5th frame, eh? I'm guessing the original framerate was a multiple of 60/5, or 12fps. So likely it was rendered at either 24Hz or 48Hz. Then I'm guessing the file was transcoded and the transcoder changed the framerate for some reason. [/quote] Hz is basically how many times your monitor refreshes, where FPS is how many frames are shown, but yeah, many use these interchangeabely because how closely tied together these are in real use. That's also why if you are doing 3D animations to be consumed on consumer devices through internet, 60Hz is still most common refresh rate, using that as deciding factor makes your animation look OK for everyone. 48 FPS render definitely sounds most likely, alternatively it was 24 FPS, which was frame doubled with interpolation [i](but if it was, then why?)[/i] But this is also why whenever I see 3D animators having no idea what I'm talking about, just use 30 FPS, ensure everything is 30 FPS at every stage. Avoids so many issues unless you're knowingly aiming at specific look or compatibility (e.g. collabing with 2D animators). Even here, if render was 30, there would've been no visual problems on neither here or 𝕏, just minor file problems.

[quote]"mairo":/users/38571 said: ... but there's additionally immense judder caused by every 5th animation frame jumping ahead with movement much more instead of consistant fashion, which is most likely caused by the animation being rendered between 30 and 60 FPS because if it was actually 60, the framerate would be halved, integer, and this would not be an issue. [/quote] Every 5th frame, eh? I'm guessing the original framerate was a multiple of 60/5, or 12fps. So likely it was rendered at either 24Hz or 48Hz. Then I'm guessing the file was transcoded and the transcoder changed the framerate for some reason.

There's something severely wrong with the file here. It's 60 FPS file, yet only every second frame updates so it's actually visually 30 FPS, but there's additionally immense judder caused by every 5th animation frame jumping ahead with movement much more instead of consistant fashion, which is most likely caused by the animation being rendered between 30 and 60 FPS because if it was actually 60, the framerate would be halved, integer, and this would not be an issue. 𝕏 source is 29.97 FPS, this is NTSC TV broadcasting standard, I'm pretty sure this was never aired in US TV? Also the same issue of judder persists.

Awesome animation love it, Keep up the great work.