267
Please Stop Making Terrible GIFs (thereallo.dev)
submitted 1 month ago by to c/technology@lemmy.world
92 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 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! :)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 6 points 1 month ago* (4 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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 2 points 1 month ago* (last edited 1 month ago) (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 1 month ago* (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 1 month ago (1 child)

    Haha, ye$, for rea$on$, I'm $ure... :D

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 1 month ago (1 child)

    I'm not sure demand for AV1 is enough to ship units

    Probably either laziness or they want to avoid software decoding in general for performance reasons

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 1 month ago*

    I think that's a reasonable way to look at it.

    It's not the route I'd take, after all, the video tag in html supports specifying multiple sources (including different formats/encodings), and with full control of the stack (they vend Safari) you could have logic on devices without AV1 hardware that prefers the AVC/HEVC/VP9 sources instead — then fallback to AV1 SW if it's the only option. That seems a better user experience than just failing to display content.

  • permalink
  • fedilink
  • source
  • parent