• @Dudewitbow@lemmy.zip
    link
    fedilink
    10
    edit-2
    10 months ago

    YouTube already has it, wouldnt hold my breath for twitch. they still havent had h265 support, and its not like thats brand new or amything.

    • @Owljfien@iusearchlinux.fyi
      link
      fedilink
      English
      1210 months ago

      Isn’t that due to that codec requiring royalties? Half the reason there is such a bit push towards av1 instead of h265 is that there is no royalties involved

    • @AVincentInSpace@pawb.social
      link
      fedilink
      English
      5
      edit-2
      10 months ago

      That’s because H.265 is patent encumbered. Firefox doesn’t support H.265 at all and Chrome only supports it if the hardware does. In order to support accepting H.265 input from streamers, Twitch would basically have to pony up the compute resources for full-res realtime transcoding for every H.265 stream to H.264 – either that or put up with a lot of bad press surrounding people not being able to stream at full res anymore.

      • @Dudewitbow@lemmy.zip
        link
        fedilink
        010 months ago

        AV1 would introduce a similar hardware requirement because not everyone even has AV1 Decode, and even fewer have AV1 encode. AV1 encode would only be available on people on gpus using the latest generation, blocking anyone buying previous generation stuff (so no AMD 6000 or older, or Nvidia 3000 or older, and non Intel Arc products).

        • @AVincentInSpace@pawb.social
          link
          fedilink
          English
          210 months ago

          All (recent) major browsers I’m aware of have software AV1 decode as standard, so the receiving end wouldn’t be a problem apart from higher CPU usage. As for encode, obviously this wouldn’t be universal – just streamers who had the computing power (hardware or software) for realtime AV1 encode would be able to take advantage of that on Twitch.

          • @Dudewitbow@lemmy.zip
            link
            fedilink
            310 months ago

            the browsers have the software, but not the hardware decode step.

            software decode, especially for mobile, would be battery draining and no streaming service would realistically would use it without the userbase having hardware decode support.

            for pcs, av1 hardware decode is amd 6000 or newer, amd phoenix apus, nvidia 3000 or newer gpus, 11th Gen intel cpus or newer.

            for mobile, its only like a small portion of the phones released in the past year and a half or so.

            for iphone, the list is the iphone 15 pro max. and for the other devices, things using the M3.

            as long as the world is a mobile first mindset, theres no way theyre going to ask evwryone on mobile to take a significant battery loss just for a higher resolution stream.