• nezeta@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I own a Mini PC with Intel N100 and it can reach 40W even when I just watch YouTube. I’m pretty happy with it though.

    • ThreeLeggedChimp@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      IIRC chrome still uses the CPU to decode VP9/AV1, you need to use firefox for full hardware decode.

      Or use h264ify

      • ksio89@alien.topB
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Wait, is it the same with Edge? My laptop iGPU (Iris Xe) has VP9 and AV1 hardware decoding, does that extension forces hardware decoding?

      • MaxOfS2D@alien.topB
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        No, hardware decoding of VP9 and AV1 works great on Chrome; I see it working with two Nvidia GPUs and a Radeon 780M

      • CasimirsBlake@alien.topB
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        On an old nuc I’m using, Firefox with YouTube is a sluggish experience and hardware decide refuses to work. A lot of folks are finding the same, likely Google pushing us away from using Firefox.

        • algaefied_creek@alien.topB
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Any NUC has H264 decode on Linux, give Linux Mint a try?

          I think tho in about:config you need to set a vaapi flag to enabled.

          • CasimirsBlake@alien.topB
            link
            fedilink
            English
            arrow-up
            1
            ·
            1 year ago

            That’s really helpful, I’ll try that thank you. Yes the decode works fine in Chromium. It’s not that, it’s Google shenanigans.