60hz monitors can support: 60, 30, 20, 15, 12, 10, 8.5, and lower (60/n)
"100hz" GIF supports: 100, 50, 33.33, 25, 20, 16.66, 14.3, 12.5, 11.11, 10 and lower
20fps and 10fps are the only smooth framerates. Picking one of these as the default would be great.

Currently the app rounds the delay, so it's not great:

Line 190 in 5880fd3

delay: UInt16(100 / fps)

The CLI version uses the alternating frame timing trick.

I plan to change the C API to take pts (presentation timestamp) instead of a delay, so that it works better when decimating frames of a video. Conversion from video's framerate already adds uneven spacing between frames. For example, you can't take e.g. 24fps video and make it anything other than 12fps/8fps/6fps/etc. without dropping frames unevenly.

That's the original article I had in mind (RIP Tumlbr): https://nullsleep.tumblr.com/post/16524517190/animated-gif-minimum-frame-delay-browser

Here's explicit info from (no longer relevant) browser vendor: https://blogs.msdn.microsoft.com/ieinternals/2010/06/07/trivia-animated-gif-timing/

Uh oh!

Allow 60 FPS? #161

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions