• kbotc@lemmy.world
      link
      fedilink
      English
      arrow-up
      78
      arrow-down
      1
      ·
      11 months ago

      Google chooses codecs based on what it guesses your hardware will decode. (iPhones get HEVC, Android gets VP9, etc) They just didn’t put much thought into arm based home devices outside of a specific few like the shield.

      • brochard@lemmy.world
        link
        fedilink
        English
        arrow-up
        14
        ·
        11 months ago

        Why wouldn’t it be my browser asking for the codecs it prefers instead of the website trying to guess my computer’s hardware ?

        • custard_swollower@lemmy.world
          link
          fedilink
          English
          arrow-up
          6
          ·
          11 months ago

          Lots of hardware lies about its useful capabilities.

          Can you run 4k? Of course. But can you run more than 4 frames a second?

          • brochard@lemmy.world
            link
            fedilink
            English
            arrow-up
            4
            ·
            11 months ago

            The browser can lie all they want, at the end of the day the user has the final word if they want to change things.

      • barsoap@lemm.ee
        link
        fedilink
        English
        arrow-up
        10
        ·
        11 months ago

        My by now rather ancient rk3399 board can hardware-decode both at 4k 60Hz. Which has nothing to do with the fact that it’s aarch64, but that Rockchip included a beast of a VPU (it was originally designed for set-top boxes).

        How about, dunno, asking the browser what kind of media it would prefer?

    • w2tpmf@lemmy.world
      link
      fedilink
      English
      arrow-up
      37
      arrow-down
      3
      ·
      edit-2
      11 months ago

      If you use any Google service, everything of yours is their business. You are their product, voluntarily.