you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 1 month ago* (last edited 1 month ago) (4 children)

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 4 child comments
  • [–] 3 points 1 month ago* (3 children)

    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 3 child comments
  • [–] 1 point 1 month ago (2 children)

    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 1 child comment
  • [–] 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