cross-posted from: https://startrek.website/post/18851336
I usually don’t post non-OCs, but this one seems relatively rare. The GIF quality was terrible, so I took the MP4 and encoded it into a high-quality animated WEBP. APNG was tempting, but when I tried that for my Prodigy meme, I ran into all sorts of issues. WEBP seems better supported.
Source: https://tenor.com/view/klingon-jump-rope-gif-7629146
Nice work … whenever anyone does work of these short little animations and video … most people have no idea how much time and effort it takes to create / recreate / manipulate / render / rerender / experiment in order to get the right combination of file size / quality / content.
Even if it isn’t OC and you went out of your way to do it … it’s still some work and knowledge.
Still one of my favorites (don’t know who made it):
And one someone cut from Very Short Treks:
I can hear these animations … in the first one I got all excited … and in the second the lights dimmed for some reason … I feel so relaxed
That second one just screams joyous Prince Adam.
The first has to be an Oom-pah.
Glorious!
Non-stop Glory!
Did you have a problem with making an APNG, or posting it? I have not tried making one, but I always post my animated images as WEBP. The only problem with that is that some Lemmy clients display animated WEBPs as just a still image of its first frame.
Mostly with posting the APNG - Lemmy doesn’t seem to natively support them in thumbnails. You CAN embed the image in the post and put a different format in the thumbnail, but that sort of beats the purpose. The caveat is you have to set the extension to PNG, or Lemmy won’t accept it.
Also, while single-frame PNGS have an acceptable compression ratios, APNG files start to get large - a dozen or few dozen megabytes. Really, it doesn’t take that much time to load most times, but it’s long enough that people might miss it.
APNG files start to get large - a dozen or few dozen megabytes
I just messed around with using ffmpeg to convert that MP4 to both APNG and WEBP, and the size difference was substantial, but definitely not that bad.
- MP4
- 60.4 KiB
klingon-jump-rope.mp4
- APNG
- 1.6 MiB
ffmpeg -i klingon-jump-rope.mp4 -plays 0 klingon-jump-rope.apng
- WEBP
- 110.9 KiB
ffmpeg -i klingon-jump-rope.mp4 -loop 0 klingon-jump-rope.webp
- WEBM
- 59.9 KiB
ffmpeg -i klingon-jump-rope.mp4 klingon-jump-rope.webm
EDIT: Oh, right, “few dozen megabytes” probably refers to some other animation you had made. Still, you are right, WEBP seems to be the way to go.
I think part of my Prodigy meme problem was I tried to encode in a bit too high a resolution (720x480). When retesting it today, I had a 49.1 MiB file, verses with a WEBP encoded at quality level 90, I got it down to 3 megabytes while still looking pretty good. I also kept having an issue with APNG white lines that I could never figure out.
Also, the WEBP was a bit larger than that - I wasn’t satisfied with FFMPEG’s default quality level of 75, so I experimented and decided on 97, getting a size of 333.8 KiB.
P.S For funzies, here’s the WEBP version of that Prodigy meme I was talking about (done in 85):
Love it, just needs to hold on the punchline a bit longer.
I can relate
- MP4