Closing the Chapter on OpenH264
54 comments
·March 25, 2025ray023
ndiddy
> But even scene groups heavily release in 265 instead of AV1.
I believe this is because scene groups don't really care about patent licensing, and there's around 5-6 years of computers with hardware H.265 decoding and no hardware AV1 decoding. I think we'll see AV1 and successors take over in 5-10 years when it's safer to assume users will have AV1 decoding.
KronisLV
> I hope the future is bright with AV1.
I bought an Intel Arc A580 and then later B580 which also has an AV1 hardware encoder, and I have to say that it's really pleasant, good enough for real time streaming, video recording even at lower bitrates (e.g. 1080p30 at ~10 Mbps is okay) and ends up saving a lot of space when compared to both H264 and H265, which previously wasn't viable because the CPU based encoder is painfully slow.
I saved a few hundred GB of space by re-encoding all of my local videos in AV1, I'm guessing it might be have been one of the better cases because most of the videos were anime instead of more detailed video like regular movies, but it worked out nicely for me! Plus, the software support is also quite good: OBS and Handbrake had no issues, neither does VLC seem to have any.
All of that makes me wish it'd become more widespread in the next decade or so, everywhere from YouTube and Twitch to even our phone cameras.
nisa
> 1080p30 at ~10 Mbps is okay
FWIW Most Streaming TV Services like Zattoo do 1080p50 using H264 using that Bitrate and while not perfect it's fine - using AV1 one could probably go way below that.
justaj
I'll continue to use h264 because it has hardware acceleration on my Thinkpad X220, whereas x265 doesn't enjoy the same luxuries on this laptop.
aftbit
It might be time to consider some new hardware. That machine is going on 15 years old now!
i80and
To be honest, if a 15 year old machine is still working fine for somebody, and h.264 is fine (if you don't care about HDR/4k, it really sort of is!), I'm not sure the benefit of suggesting somebody junk a machine
out_of_protocol
vp9 is widely used (e.g. YouTube is mostly vp9, av1 and fallback h264) and not much worse
Thaxll
AV1 is extremely slow to encode last time I tried.
i80and
My guess is you were using the reference AOM encoder. This is actually a real branding problem! It was never designed for encoding speed, and it shows.
SVT-AV1 is the production encoder you should be using. It's high quality and fast in software, and should really always be the default.
spongebobstoes
For now most of the focus has been on the slow encodes, but in theory it can match h264 for speed and quality on encoding. In practice I've seen it get very close already.
alabastervlog
I avoid AV1 sources for anything I care about, because of film grain synthesis.
p1mrx
Does AV1 just emulate the film grain from the source video, or are people adding/customizing the grain when encoding?
alabastervlog
Emulates it, which strikes me as extremely silly. The original grain is in the film itself, it's part of it, it's what the image is made of. Fake grain is just noise. Either denoise it or keep the real grain, I have no interest in fake grain.
unit149
[dead]
Latty
Why? It's a feature you have to explicitly turn on when encoding, and I've not seen people using it for most stuff.
alabastervlog
I can't know if it was used in advance, so favor h265. Which is far more common (and so's h264) so it's not much trouble to avoid AV1.
msanlop
including digital footage with film grain added in post?
alabastervlog
I don't watch a ton of films with noticeable fake grain. Even the ones that do fake it, it's barely perceptible, so I wouldn't care on those—not many of them are emulating the huge, obvious grain of high-sensitivity '60s and '70s film, for instance. A lot of what I watch is from the '90s or earlier, so the grain's real.
jsiepkes
Isn't it already patent free in Europe? You can't patent algorithms in Europe. For example MP3 was royalty free in Europe because there was no patent on it.
FuriouslyAdrift
Weird considering a ton of codec patents are held by Fraunhofer, which is based in Germany. https://www.iis.fraunhofer.de/en/ff/amm.html
Formerly MP3 (expired 2017), MPEG-H Audio, xHE-AAC, EVS, LC3/LC3plus, Symphoria, Sonamic and upHear
WhyNotHugo
Too often the organisation behind projects is in the US, so is restricted to only what is legal in the US.
I suspect that’s the case here. IIRC, the Freedesktop servers are hosted in the US, so are also affected by what’s legal there too.
And in this case, they were shipping a userspace for their sandboxes, which is a dependency for many others. If it contains code that cannot be distributed in the US, then anyone in the US will have to pick an alternative.
ChocolateGod
> the Freedesktop servers
Think they just moved to Hetzner.
NooneAtAll3
seems like another reason to hop onto "move your servers to Europe" bandwagon
ksec
So apart from US, H.264 High Profile will be patent free by this August!
xfp
Of h.264, h.265, vp8, vp9, and av1, h.264 is the only codec with consistent support across all of chat/messaging clients, browsers, smart TVs/phones, tablets, and streaming devices. The population of active, supported devices and software is much larger and much older than people realize. As such, it remains the only viable video codec if you don't want to be forced to provide multiple encodings.
hcfman
It is possible to do something like webrtc without using one of h264 or h265 and have it work on all browser versions ?
Normally, apple quicktime containers with h264 payloads are playable everywhere. If you drop h264 or h265 there is no such play anywhere container available anymore right ?
cbhl
VP8 should be required by the base WebRTC spec, but some devices only have hardware acceleration for H.264 so you should test the actual performance before changing codecs. Also consider using VP9 / AV1 if you know all the devices in a call support it and are fast enough to encode/decode it.
https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Fo...
ZeroGravitas
> Which codecs can be within those tracks is not mandated by the WebRTC specification. However, RFC 7742 specifies that all WebRTC-compatible browsers must support VP8 and H.264's Constrained Baseline profile for video, and RFC 7874 specifies that browsers must support at least the Opus codec as well as G.711's PCMA and PCMU formats.
https://developer.mozilla.org/en-US/docs/Web/Media/Guides/Fo...
daneel_w
Correct. The most supported container and codec families are those coming out of the MPEG - .mp3, .m4a, .mp4, H.264, H.265 etc. - because they are the products of a giant standards effort. A lot of modern TVs and set-top boxes will accept content in e.g. the Matroska container, and VP/AV video content, but unfortunately support still isn't at the level of the MPEGs.
userbinator
The binary would be downloaded on the end user’s machine, inside a sandbox and then the “recipe” would be executed to create a working extension. This avoids various “redistribution” restrictions entirely since we aren’t shipping the binary itself.
That makes me wonder, why not just download the source code and compile it. You're definitely not distributing any binaries that way.
prosody
As I understand it, Cisco licenses the relevant patents and sublicenses them gratis to every user who uses Cisco’s binaries obtained from Cisco directly and not redistributed (thus also the difficulties in the article with working with Cisco’s unmaintained web server). The sublicense doesn’t apply to binaries built independently from source. I suppose this was imposed by the patent holders.
boricj
Can that library be rebuilt in a reproducible manner? If so, what's the difference between the library hosted by Cisco and a locally built one that is identical bit-for-bit? Is there any mechanism to ensure that the library was genuinely downloaded from Cisco rather than procured through alternative channels? If the Cisco server is turned off tomorrow, how can one tell if a copy of the library wasn't downloaded from the Cisco server while it was available?
I'm most likely missing a lot of crucial context, but it appears to me that this peculiar licensing scheme was a compromise made between lawyers that makes little practical sense on a technical level. That, or I'm far too chaotic for such nonsense.
mod50ack
The difference is legal, not technical. You don't have the right to redistribute copyrighted material with permission, except according to exceptions to copyright law (which are narrow enough to not apply here). Cisco gives permission for users to use the software only if downloaded directly from Cisco, and doesn't grant anybody permission to mirror and redistribute it.
Can you tell if a copy was downloaded from Cisco directly? No. Does it make a technical difference? No. But those are the rules Cisco chose, and so there it is.
One potential reason I can think of for this happening is Cisco being required to count the number of downloads of the software (or something like that). But, in the end, there's no requirement that there be logical sense to a rule like this.
mastax
So they decided to just ignore the patent problem? Fair, I guess, that’s what other open source projects do.
Why hasn’t canonical been sued by MPEG-LA et.al? Are they no redistributing compiled FFMPEG for commercial purpose?
null
robert_foss
It really is too bad AV1 hasn't had a successor yet. x264 and x265 are patent ridden scourges and should be avoided wherever possible.
i80and
Does AV1 need a successor right now? At least as of some years ago SVT-AV1 was stronger than x265 on both software encoding speed and quality/bitrate[1], and a successor would reset the timer on getting hardware decoders rolled out.
[1] https://medium.com/@ewoutterhoeven/av1-is-ready-for-prime-ti...
daneel_w
The problem with the patents are largely misunderstood. Most importantly the patents do not directly apply to the individual consumer downloading and decoding such audio/video content. The patents only apply to commercial settings - the sales of software that can encode or decode audio and video in the MPEG formats, and sales of audio and video content encoded in those formats. This is why Mozilla made a big fuss over not wanting to include H.264 decoding in Firefox years ago, because they feared they'd have to spend a bit of their money since they are after all a commercial endeavour. No, really, it was never about wanting to "protect" users, it was always about their earnings. You can happily encode AAC audio and H.264 video and share it free of charge with everyone, and they can always listen to and watch that content, without any worries.
And pardon the nitpick but it's H.264 and H.265, not x264 and x265.
whizzter
Seems like the last h264 patents expires in about 5 months, silly to start moving around to options that might have submarine patents when we'll have something functional that's patent free in quite a short time.
ddtaylor
I encode a lot of my media as h264 because it makes it easy for my kids to stream it from Jellyfin without transcoding.
mvanbaak
unless the content is 4k. Then you want h265 ;P
godzillabrennus
Why?
daneel_w
H.264 does just fine with 4K. If you know what you're doing you really don't need to throw 10 Mbit/s at it to get crisp quality.
(p.s. I'm fully onboard with H.265 being fantastic, it's amazing to see what e.g. x265 can do for it, being able to provide practically identical output at 30-50% lower bitrate. I'm just saying that H.264 isn't in any way incapable.)
ZeroGravitas
They've been working on it for years but I'm not sure there's any great need for it right now. The various MPEG alternatives seem to be eating themselves with patent infighting and fragmentation.
unethical_ban
edit: Got confused by Wikipedia.
It says AV1 is open source and royalty free, and all modern hardware seems to have hardware decode for it. It doesn't seem any of the big players are realistically worried about bogus patent claims.
I hope the future is bright with AV1. But even scene groups heavily release in 265 instead of AV1. Hardware support is going to get better over the years and hopefully everyone will just use AV1 and leave this license BS behind.