top 50 comments

sorted by: hot top controversial new old
[–] 96 points 1 month ago* (7 children)

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.

  • source
  • hideshow 14 child comments
  • [–] 61 points 1 month ago (1 child)

    Counterpoint: GIFs loop by default in basically every app, WEBM doesn't

  • source
  • parent
  • hideshow 2 child comments
  • [–] 35 points 1 month ago* (last edited 1 month ago) (20 children)

    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:

    Image

    Edit: switched to an example with simpler decode requirements.

  • source
  • parent
  • hideshow 27 child comments
  • [–] 32 points 1 month ago (3 children)

    Your demonstration is a sluggishly loading static image on my end, so I guess support isnt that widespread :P

    (Im using the app "Summit")

  • source
  • parent
  • hideshow 6 child comments
  • [–] 15 points 1 month ago* (last edited 1 month ago)

    I checked that app's source code, and basically they're doing their own avif decode call instead of relying on a browser/webview to handle it. So essentially they forgot/don't know/don't intend to implement animated avif. Looks like they also use the aom reference decoder instead of using something faster like dav1d.

  • source
  • parent
  • [–] 5 points 1 month ago* (last edited 1 month ago) (1 child)

    (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! :)

  • source
  • parent
  • hideshow 2 child comments
  • [–] 6 points 1 month ago* (8 children)

    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.

    Image

  • source
  • parent
  • hideshow 9 child comments
  • load more comments (7 replies)
  • load more comments (13 replies)
  • [–] 18 points 1 month ago* (last edited 1 month ago) (4 children)

    I’ve honestly given up on support of new formats.

    Here we are, 2026, and brand new software like Lemmy:

    • Doesn’t support AVIF

    • Doesn’t support JXL

    • Doesn’t support WebP

    • Won’t upload short, small videos either.

    Meanwhile:

    • Many clients won’t play animated WebP

    • Most clients won’t play APNG

    • Many won’t load AVIF

    • Basically only Apple/Safari will load JXL

    • VP8/VP9/AV1 support in video isn’t universal

    What am I supposed to do?

    I used to send support requests over this, but I’ve given up. We are going to be stuck with SDR JPEGs and blocky GIFs forever, especially since media format literacy seems to be globally.

  • source
  • parent
  • hideshow 4 child comments
  • load more comments (4 replies)
  • [–] 10 points 1 month ago*

    I used to love optimising images in gif format. I would make like 4–30kb memes and animations for my friends in Photoshop CS2. It's actually extremely efficient and lightweight if you do it right… You have cool tools like transparency between frames and unbroken colour blocks don't take any additional storage space. There's nothing wrong with gif.

    The problem is how people use them. We take a live action video file and shove it through an automated converter tool that doesn't give a shit about efficiency and will do a complete repaint between frames and use 256+ colour palette. Then you end up with an ugly dithered overcooked piece of shit 50mb 10 second animation. Gif was not designed for this…

  • source
  • parent
  • [–] 75 points 1 month ago (1 child)
  • [–] 62 points 1 month ago (1 child)

    Most people do this:

    ffmpeg -i video.mp4 output.gif

    ...no, most people have never heard of ffmpeg and throw it in an online converter.

  • source
  • hideshow 2 child comments
  • [–] 27 points 1 month ago (3 children)

    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.

  • source
  • hideshow 4 child comments
  • load more comments (2 replies)
    [–] 21 points 1 month ago (1 child)

    Thanks. This is going straight to my 'cool info to never be used' pile.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 13 points 1 month ago (1 child)

    As much as everyone likes to trash on it, this is part of what webp is for. Animated, loopable images at super small sizes that display on just about anything that runs a browser.

  • source
  • hideshow 1 child comment
  • load more comments (1 reply)
    [–] 13 points 1 month ago

    Don't get mad at people for using logical command line switches.

    Get mad at ffmpeg for trash defaults.

  • source
  • [–] 11 points 1 month ago
    [–] 10 points 1 month ago (1 child)

    I wish the article had examples. It would be cool.

  • source
  • hideshow 2 child comments
  • [+] 10 points 1 month ago* (last edited 1 month ago)
    [–] 7 points 1 month ago

    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.

  • source
  • [–] 6 points 1 month ago

    Really interesting and useful read, thanks.

  • source
  • [–] 5 points 1 month ago
    [–] 4 points 1 month ago
    [–] 4 points 1 month ago
    [–] 3 points 1 month ago (1 child)

    A lot of that is mostly the fault of the technology. But we still like it anyway.

  • source
  • hideshow 2 child comments
  • [–] 7 points 1 month ago (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 1 month ago

    Nobody: zzzzz

    Me reading about 256 bit color conversion at 3 am: 🤔🥱🤓🤷💀🐩

  • source
  • load more comments
    view more: next ›