(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.
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.
(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.
This doesn’t work for me but the original one you posted does (Voyager, iPhone 14 pro)
Very interesting, thank you!
Random Android phone on Voyager; yes.
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
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
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.