you are viewing a single comment's thread
view the rest of the 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) (15 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 30 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* (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

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

  • 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.

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

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

  • 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

  • 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.

  • source
  • parent
  • [–] 1 point 1 month ago

    Thanks for bringing this format to my attention. I opened it in a browser and it's pretty sweet.

    Hopefully app support will grown over time... Otherwise it'll be .gif 'till the end.

  • source
  • parent
  • [–] 1 point 1 month ago (1 child)

    Let me know when I can text one of these to someone

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

    I do regularly. However apple users are largely the bane of this. Apple's support for things can be very slow and spotty. As long as you keep it extremely old and basic. Say h264 they'll be able to see. A lot of apple mobile devices could support h265 but apple doesn't. My last couple of mobile devices have supported it for nearly a decade. But apple enabling it on their mobile hardware hasn't been anywhere near that long. Apple will hopefully have AV1 support common by the time AV3 is released and AV2 widely supported by the 2030s.

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

    Apple only supports avif on paper and doesn’t actually support avif in iMessage in practice. It won’t display properly and they don’t care to fix it.

    On the Android side Google Messages Doesn’t appear to support avif at all

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

    Oh yes with respect to Avif you are correct. I was more referring to multimedia messages in general. But you are correct about Avif. That format in particular is not well supported a lot of places. I know Linux is probably one of the few areas it sees much. Windows is a much different story and I'm sure Apple desktops as well.

  • source
  • parent