OBS Studio Lands AV1 & HEVC RTMP Streaming Support

[Quackdoc]

tambre :
More on topic, if my friends were on constrained bandwidth I would also be concerned that they wouldn't be able to efficiently decode anything newer than h.264.
It's great that OBS is moving towards integrating support for newer codecs, but when creating media one has to also take into thought the experience of the majority of one's end users. Very few are going to have hardware decoding for AV1 or HEVC unless you're targeting Apple device users.

YT transcodes everything anyways so it's not something the uploader has to worry about, you can stream HEVC and AV1 to YT and it will still get transcoded to AVC/VP9, meaning right now, this is a massive update for MANY streamers. the difficulty in which encoding/decoding av1 really isnt high at all anyways in the first place. lots of people with hardware availible but with bandwidth that necessitates AV1, (IE. bandwidth cap, 3g/4g etc.)

[edxposed]

Except for some antiques in museums, all modern devices should have hardware-accelerated HEVC encoding/decoding capabilities, the problem is apparently with some stupid distro that disables the HEVC VAAPI

[Quackdoc]

Except for some antiques in museums, all modern devices should have hardware-accelerated HEVC encoding/decoding capabilities, the problem is apparently with some stupid distro that disables the HEVC VAAPI

are you willing to pay extra for HEVC?

[BrokenAnsible]

are you willing to pay extra for HEVC?

Some people are every time they buy Nvidia.

[Quackdoc]

Some people are every time they buy Nvidia.

it would be an interesting experiment to see if people would be willing to pay, maybe via flatpak or something xD

[hajj_3]

Actually on Twitch / YouTube / other livestreaming sites which are where the vast majority of RTMP usage exists in terms of bandwidth and cost

I think twitch uses HLS.

[piotrj3]

Some people are every time they buy Nvidia.

Not just Nvidia, AMD and Intel all support H265 hardware encoding and it is exposed in propertiary SDKs/APIs. Literally OBS or FFMpeg can use AMD's or Nvidia's or Intel's hardware encode to use on the fly H265 to record stuff to file. Fact some distros remove such feature in open source drivers makes a good question if there is licensing issue here.

If it had to be done then it is good question what should be done. Some propertiary addon that installs and cooperates with open source drivers? No clue.

[piotrj3]

are you willing to pay extra for HEVC?

You already are moment you buy hardware from Nvidia/Intel/AMD. Fact it exists in nvenc, amd VCE, Intel QSV all expose that feature. Just not a single clue why opensource drivers cannot have it.

[You-]

Maybe the clue is that its not hardware or software related, but licensing related?

The licence requires the person who puts the last piece together to pay the licence. So if you have a distro that includes it, it is the distro that needs to pay, not the manufacturer. The licensing even prevents the GPU manufacturer from paying even if it wanted to without jumping through hoops.

The solution is for the hardware manufacturer to provide the missing bits. It could be a bit like the openh264 repository - AMD will need its own and intel too, and add them to the distros to get the final bits from there.

But that needs coordination and willpower from the manufacturer to do that work and to work with distros to get it integrated.

[Quackdoc]

You already are moment you buy hardware from Nvidia/Intel/AMD. Fact it exists in nvenc, amd VCE, Intel QSV all expose that feature. Just not a single clue why opensource drivers cannot have it.

its been covered extensively now, both on the forums in the original post about it, as well as elsewhere that you dont. you pay for what the vendor ships. and that might not even be that true. distros are liable for payment under HEVC's and possibly AVCs licenceing terms. though the baseline AVC profile should be copyright free soon IIRC