uploading this to Mastadon was unnecessarily hard!
1500x1500? nope
1280x1280? nope
720x720? sigh
I had also added a slight delay on the first and last frame for the bounce, but this seems to show up as a delay on the second and second-to-last frames which is annoying, testing this GIF again here, maybe a client issue? I’m on Ivory but if you see a weird stutter step on another client let me know
@burritojustice The delay value associated with a GIF frame is after the frame, but that's not how MPEG timing works. So when converting from GIF to video you have to duplicate frame 0 as frame N with delay 0.
It also doesn't help that GIF measures that delay in 1/100th sec, which cannot represent normal frame rates of 1/30th or 1/60th sec as an integer.
@burritojustice My blog converts GIFs to MP4s for display in order to save bandwidth, so I had 20 years of weird GIF test cases that I had to figure out how to make work, since as you have discovered, ffmpeg just throws up its hands.
Add comment