• biscuitswalrus@aussie.zone
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    10 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
      3
      ·
      10 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
        ·
        10 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
          ·
          10 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
            ·
            10 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.

  • Wes_Dev@lemmy.ml
    link
    fedilink
    English
    arrow-up
    5
    ·
    10 months ago

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

    IF

    IT

    KEEPS

    HAPPENING

    • labsin@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      2
      ·
      10 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.

  • originalucifer@moist.catsweat.com
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    10 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.