You must log in or # to comment.
I wish the article had examples. It would be cool.
Please stop making gifs at all. It’s a terrible format that creates massive files that look like shit.
Webm is supported almost everywhere now and manages better quality at higher framerates and smaller file sizes.
“…massive files…”
I thought the file size was part of the format specification, no?
Counterpoint: GIFs loop by default in basically every app, WEBM doesn’t
Can just use avif instead, it holds an AV1 stream and acts like gifs/images do WRT looping — also very broad support (more than AV1 in WebM containers).
Demonstration:
Edit: switched to an example with simpler decode requirements.
It’s unfortunately not that simple. The AVIF doesn’t load at Jerboa, for example :/
Fwiw it works on the desktop’s alexandrite ui and on the thunder app
on boost its a little slow but time quality.
better than most moving images in comments!
Your demonstration is a sluggishly loading static image on my end, so I guess support isnt that widespread :P
(Im using the app “Summit”)
Static image, also Summit.
(on Arctic on ios) the uploaded image displays as a static image for me. Even clicking on it and waiting, it doesn’t seem to animate :T
Edit: I checked again through the Voyager app, and it did indeed load, though it took around 45-60 seconds* for it to get through the entire animation before it started looping again, albeit at the same speed as the first playthrough.
I chalked it up to the outdated hardware, as you mentioned in your reply. Cheers! :)
Apple has limited support for AV1 streams (yes, even for software decode) unless on very recent hardware. Here’s an AV1 stream inside a webm container for comparison, would be interesting to see if that works over the avif container on your stack.
Ah yeah, that would explain it - my phone is now pretty outdated (I’m on a 12) - I clicked on the image link in your response but it didn’t load for me, unfortunately.
I’m not sure if that’s a result of my outdated hardware or if I perhaps clicked on it before it had a chance to process your upload, but you seem much more knowledgeable than I, so I’m going to assume it’s my hardware. I appreciate the response and the second attempt, though! :)
It’s an intentional behavior by Apple. Basically they just don’t support AV1 videostreams unless the hardware you’re using has a hardware decoder (read: very new). They could support it using software decode (what browsers typically do for AV1 inside avif containers) but… for whatever reasons don’t.
Haha, ye$, for rea$on$, I’m $ure… :D
For the record, this is static in my Lemmy app (Summit).
Webm is supported almost everywhere now and manages better quality at higher framerates and smaller file sizes.
Anybody who has compared animated WebM vs animated JPEG XL?
the same file without visual quality loss could be a 156.79 KiB webp file, saving energy, internet, and storage costs
I just tested this with a 8-second, 35MB mp4 video.
The “don’t do this” command made a crappy looking 316MB gif.
The suggested pair of commands, using the palette file, made a 57MB very nice looking gif.
Seems legit to me but I’m not, as you say, an expert.
that’s still massive, an animated webm will probably be more useful
Thanks. This is going straight to my ‘cool info to never be used’ pile.
Really interesting and useful read, thanks.
I always liked to use Photoshop with the ‘save for web (legacy)’ export. Gives you a handy preview of how big it will be and lots of options.
ffmpeg <3 good info here, also give Gifsicle a look if you need help getting your gifs smaller
A lot of that is mostly the fault of the technology. But we still like it anyway.
Gif is indeed a shit format for the purpose.
Video codecs are downright magical and everything down to your average toaster packs a hardware decoder for h264, so this is the bare minimum we should actually be using for this use-case.
I know that’s hyperbole, but I’ll be cold in the ground before a “smart” toaster is allowed in this house.
deleted by creator
