#have a set of screenshots while i redo my gifsets now that i know how to edit them better

[casino-lights]

it's hardly a fair fight when one of us has a horde of venatori behind him.

it's hardly a fair fight when neither of us wants the other dead.

[sleepymarmot]

I haven’t giffed for a while, so making the previous post was a bit of an adventure.

I started this gifset in February 2021. Back then I ripped every frame and the gifs were too big for tumblr, so I had to delete every other frame by hand. It looked so choppy that I put the post on ice, and it got buried under other drafts. Evidently I found the post again months later but didn’t fix it and left it to rot again.

I found the post again this week and almost published in that state, but thought it’d be too embarrassing to post a gifset with every second frame in 2023. I then tried to remake it in proper quality. I discovered that I had one of the gifs ripped with every second frame, and had to re-rip it again (and remember how to crop them). For some reason, the new screenshots were brighter, so I had to use a different coloring for them. I also had to split that gif into two, but that’s easy.

The gifs were still way past the Tumblr limit, and I was on the brink of losing hope and shelving the post again when I realized that I can just reduce the number of colors. This is b/w! There are 64 and even 32 colors per gif in that post and it all looks perfectly fine. So my big problem from two years ago was finally solved. (Too bad this solution would not work with normal color gifs.)

The original version was also awfully slow. For the new one I started experimenting with frame delays since I’m unfamiliar with giffing every frame. At first I tried to abandon frame animation altogether and set the FPS on the timeline the same as original video, but that didn’t work (in two different ways). Then I realized that gif exporting ruins frame delays anyway, rounding them up/down to either 0.03 or 0.07. 0.03 looked perfect in my desktop image viewer but too fast on Tumblr in the browser. 0.05 looked too slow. Then it finally occurred to me to do the math, and 1 second / 23.976 fps indeed equals 0.04 (rounded). So I adjusted the gifs to have 0.04 as frame delay and it still looks wrong somehow, even though objectively it should be the best option.

By the way, I had to carefully replace gifs one by one in the original post buried like fifty pages deep within my drafts, and not just because I didn’t want to make a new one: that draft is in the legacy photo post format, and I don’t have access to it for new posts anymore.

After finishing and uploading all that, I realized that I never cropped out the black border, and it’s quite visible at the edges of the gifs. But I already wasted way too much time to go through every gif again.

In the end, the only thing I had to redo from scratch was the final gif (now split in two). For all the others, I used the same psd, adjusted the export settings, then redid the frame delay of the exported gifs. The real time-consuming part was not the editing process itself, but figuring out what I needed to do.

All this was for an extremely simple gifset, by the way. The kind that requires no actual creativity or hard work, only a bit of technical know-how. If you know what you’re doing, and not blindly poking at the settings you’re not used to, it should take no time to make. I just want to share how much I’m overthinking everything. (And also to journal for my own sake, because this has been An Experience.)