#gifski

[doraemonfanclub]

Did you say expressive eyes? The kind of expression that screams "HALP PLZ!?!"

[doraemonfanclub]

Doraemon free falling, send halp!

[doraemonfanclub]

Doraemon as Agent Smith. What an unexpected cross-over!

[doraemonfanclub]

Doraemon, all the feelings at once.

Not my favorite rendition of Doraemon, the drawing felt overly computerized, but I love his expressive eyes.

[goodgifswithfreetoolschallenge]

Hi! First of all, I want to thank you. Your recources are exactly what I was looking for, amazing!

I don't know if you can help. I downloaded the GUI version of Gifski (Windows) to try it out, but the current version does not allow you to drop in mp4 files, only png. So I converted the mp4 into png, but the app doesn't give me the chance to adjust anything. I tried to change the fps, but I only get a super sped up gif and I also can't adjust the height of the gif.

So I tried downloading the CLI version but my laptop won't open it because it says it's a danger to the computer.

Do you have any idea what happened? Why the app is so reduced and now? Could I download an older version or is the problem that I use Windows?

Once again, huge thanks. I'm determined to keep going and figuring out some way to finally make better gifs!

Hey there! Hmm... Gifski did not have a GUI version for Windows when I made my tutorial I think, so I only just now downloaded it to take a look. It seems very different from the Mac version!

One thing that could be going on (depending on how you converted to .png) is that the proper fps to set in gifski should be determined by the rate at which you captured .pngs from the .mp4 file. For example, you'd need to capture .pngs at 20 fps and set the Gifski fps to 20 to get a gif that looks "normal" speed, or capture .pngs at 30 fps and set the Gifski fps to 30, or etc.

As for the CLI version of Gifski, instead of downloading the binary files, I would use a command line package manager. On the gifski website, they recommend installing Rust then typing the following in your computer's terminal:

cargo install gifski 

I'm not sure how much that helps, but I hope it helps at least a little!

[doraemonfanclub]

Doraemon exercising with his gadgets.

[goodgifswithfreetoolschallenge]

TOOL TUTORIAL 7

The Best of Both Worlds: FFmpeg Sharpening + Gifski Compression

I don't think I've shared the script I am now consistently using to turn my DaVinci Resolve clips into GIFs.

I am now using FFmpeg and Gifski scripts in combination. For the best balance of sharpness and compression.

After pointing my terminal/shell (Terminal on Mac and Linux, Powershell on Windows) to the folder where all my clips are, I paste these two commands into the shell/terminal,

for i in .mp4; do ffmpeg -y -i "$i" -filter_complex "smartblur=1.5:-1,unsharp=la=1.5" sharp_${i%.mp4}.mp4; done for i in sharp_; do gifski --fps 22 --width 540 --quality 100 -o ${i%.*}.gif "$i"; done

You can past them in at the same time or paste in one then the other.

The first script makes new copies of your clips and sharpens them, giving them the prefix "sharp_". The second script compresses those sharpened clips into GIFs.

In the second script, the numbers to the right of the fps, width, and quality flags can be adjusted to compress GIFs further or scale them down. (540 is the appropriate width for a single column set).

[goodgifswithfreetoolschallenge]

Two different settings here.

The top clip was rendered and optimized into a gif with this code:

for i in *.mp4; do ffmpeg -y -i "$i" -sws_dither bayer=5 -filter_complex "fps=30,scale=540:-1:flags=lanczos,smartblur=1.5:-0.55" gifs/${i%.}.gif; done

Then the second one using this code:

for i in *.mp4; do ffmpeg -y -i "$i" -filter_complex "smartblur=1.5:-1" gifski1/${i%.}.mp4; done

Which sharpens the frames of the MP4 clip, then this to make the gif:

for i in *.mp4; do gifski --fps 23 --width 540 --quality 100 -o ${i%.*}.gif "$i"; done

The differences are way more apparent on mobile. The bottom gif has inkier blacks, overall handles the original colors better, and doesn't have the very obvious dithering that the top gif does. However, it's also a larger file size at 7.3MB vs. 4.3 MB—but those are both pretty good amounts of compression for a 3.25 second gif. If you wanted to do a long gif (like 5-6 seconds) you could probably still upload it using the first code.