• kbotc@lemmy.world
      link
      fedilink
      English
      arrow-up
      77
      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.

  • originalucifer@moist.catsweat.com
    link
    fedilink
    arrow-up
    104
    arrow-down
    3
    ·
    edit-2
    11 months ago

    this prolly wasnt a bad decision early on… why push something to a population who cant utilize it… but shit changes fast, google.

      • originalucifer@moist.catsweat.com
        link
        fedilink
        arrow-up
        15
        arrow-down
        2
        ·
        11 months ago

        was it ignorance or malicious intent?

        if it was a person, i would try and assume ignorance… im not sure google the company deserves such respect

        • villainy@lemmy.world
          link
          fedilink
          English
          arrow-up
          27
          ·
          11 months ago

          Or it’s a company so fuckoff huge that one department (Chrome on Android) couldn’t get a bug report escalated in another department (YouTube). Eventually they just put in a UA workaround while the bug rots in a backlog somewhere. Common enterprise bullshit.

          Or the Chrome on Android team didn’t even bother reporting the issue to YouTube and just threw in a cheap workaround. Also common enterprise bullshit.

          • lolcatnip@reddthat.com
            link
            fedilink
            English
            arrow-up
            8
            ·
            edit-2
            11 months ago

            Bingo. When I was a Chrome developer working on video stuff, we mostly treated YouTube like a separate company. Getting our stuff to work with theirs was a priority, but no more than, say, Netflix. We pretty much treated them as a black box that consumed the same API we provided for everyone.

      • ericswpark@lemmy.ml
        link
        fedilink
        English
        arrow-up
        10
        ·
        edit-2
        11 months ago

        Could be that the developers for the HiSense TV just copy-pasted whatever UA into their browser codebase and called it a day.

    • labsin@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      7
      ·
      11 months ago

      This issue was detected when running Firefox on Linux on Apple silicon. Firefox on Mac just identifies as x64.

      It’s probably not on purpose by YouTube. It’s stupid they put restrictions on some heuristics to begin with but maybe because otherwise people would think YouTube is not loading properly while it’s the software decoding on the not capable arm PC that can’t handle the resolution.

  • Wes_Dev@lemmy.ml
    link
    fedilink
    English
    arrow-up
    14
    ·
    11 months ago

    Repeat after me kids. It’s not an “oversight”, or “mistake”, or “bug”, or “misunderstanding”…

    IF

    IT

    KEEPS

    HAPPENING

  • biscuitswalrus@aussie.zone
    link
    fedilink
    English
    arrow-up
    14
    ·
    edit-2
    11 months ago

    Seems like my Samsung TV app is being hit by stuff too, I had 5 unskippable ads and can’t seem to get stable 1080p at 60fps any more despite gigabit fibre and cat6. Meanwhile getting 4k on my YouTube app on Android on WiFi.

    Go figure.

    YouTube is so desperate to fight this war that they’re harming legitimate watchers meanwhile my rockpi running Android TV seems to keep running sTube just fine.

    • Avg@lemm.ee
      link
      fedilink
      English
      arrow-up
      5
      ·
      11 months ago

      The nic on TVs tend to be awful. I can barely break 100mbps on my lg wired or wireless.

      • c10l@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        11 months ago

        100mbps should be enough for a few 4K streams, and I imagine you’re not streaming more than one thing to your TV at any given time.

        • Avg@lemm.ee
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 months ago

          4k yes, 4k hdr is where it becomes limiting…from what I’ve read.

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

            Perhaps, and I’ll readily admit my ignorance on this.

            That said, I doubt the HDR overhead would be any larger than the equivalent baseline SDR content.

            If my intuition is right, depending on other factors like compression you could still fit at least 2 streams on that bandwidth.

  • atocci@kbin.social
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    11 months ago

    Does this apply to Windows on ARM as well, or is it just Linux specifically for some reason?

      • atocci@kbin.social
        link
        fedilink
        arrow-up
        2
        ·
        11 months ago

        That’s what I figured, but every article I’ve seen on this calls out Linux specifically. I’ll have to give it a try from my Surface Pro X when I get home and test.