Live data from Hacker News

H.266/Versatile Video Coding (VVC)

newsletter.fraunhofer.de

111–120 of 435 posts

Re: H.266/Versatile Video Coding (VVC)

#111
post #54

Earlier quoted context omitted.

The situation with AV1 is "we are in middle of minefield and nobody got mine-clearing gear". They can be reasonably sure they do not infringe known patents from certain Patent Pools and patents declared as part of MPEG-LA bundles. They can't provide reasonable data that they do not infringe on any submarine patent, something that killed 3 attempts by MPEG-LA to provide a royalty-free codec for the web - all that was…

> The situation with AV1 is "we are in middle of minefield and nobody got mine-clearing gear". That's true of every new video codec. It didn't stop the use of H.264 or VP9 or even HEVC. Multiple companies have now rolled out AV1 into production. We'll see what happens.

When I wrote that I didn't know about retaliation clauses in AV1 patent pool license. That said, a huge chunk of patents involved in all MPEG standards (AVC, HEVC, etc.) meant that if you tried to go after them, you might have lost licenses necessary elsewhere, so it's all a question of risk analysis for someone who wants to torpedo AV1 with a patent.

What's wrong is claiming that AV1, VP9, VP8 are "patent-free". They are not.

Re: H.266/Versatile Video Coding (VVC)

#112
post #93

Earlier quoted context omitted.

Software patents aren't a thing in ~~Europe~~ a few European countries. Sure it's difficult to ignore the American market for a company, but an independent developer could specify a state of the art video codec without thinking about patents. Edited because I didn't know that some European countries accept software patents.

Software patents are a very complex thing. For example, many countries in EU do not allow patents on software, but that's not something you can claim to be true for all of them - at least before Brexit, since iirc UK was pretty happy to provide software patents. Then there's a case where if you're really willing you can, as far as I understand, force a patent dispute through WTO, with possibility of patent valid in U…

What really annoys me is that Article 52 of the EPC explicitly excludes software from patentability. It couldn't be more clear in its language (to me). But when I talked to a patent lawyer about this a while back he said didn't really mean that and software could and is easily patented.

https://en.wikipedia.org/wiki/Software_patents_under_the_Eur...

Re: H.266/Versatile Video Coding (VVC)

#113
post #53
post #9

Naively hoped I'd read 'this will be released to the community under a GPL license' or similar. Instead found the words 'patent' and 'transparent licensing model'. I appreciate that it costs money and time to develop these algorithms, but when you're backed by multi-billion dollar "partners from industry including Apple, Ericsson, Intel, Huawei, Microsoft, Qualcomm, and Sony" perhaps they could swallow the costs? It…

What you're looking for is the AV1 codec, which finalized a year and a half ago and will likely see much wider adoption, simply because none of the members want to pay royalties. https://aomedia.org/av1/ https://aomedia.org/membership/members/ AV1 decoding has already been in Chrome and Firefox since at least a year ago. We're just waiting for hardware decoding and encoding support now, which should start appearing t…

Your comment was deaded. I vouched for it because I don't see anything that looks obviously inflammatory/incorrect, but I noticed that a large fraction of your comment history is also dead. You might want to look into that, since most of the dead comments also looked fine to me.

Re: H.266/Versatile Video Coding (VVC)

#114
post #5

that sounds great, but this is a press release with no real technical details. can anyone in the know add some context? for instance, whats the tradeoff? I assume more CPU? webrtc based video chats are all still using h264, did they not adopt 265 yet for technical or licensing reasons? what is the likelihood of broad browser support for h266 anytime soon?

H.265/HEVC takes about ten times as much computation to encode than H.264 [1], so H.264 still has legitimate technical use cases, even with licensing/patents aside. This makes it great for a company like Netflix or YouTube, but less good for one-to-one and/or battery sensitive use cases like video calls. However, specialized chips help, and some mobile devices can record in HEVC in real time (mine from 2019 can). I b…

iPhone 7 onwards[1], Qualcomm Snapdragon 610 onwards[2], and Intel Skylake and later CPUs[3] can all encode and decode H.265 in hardware to varying profile levels.

1: https://support.apple.com/en-gb/HT207022

2: https://www.qualcomm.com/snapdragon/processors/comparison

3: https://trac.ffmpeg.org/wiki/Hardware/QuickSync

Re: H.266/Versatile Video Coding (VVC)

#115
post #106
post #95

Earlier quoted context omitted.

As others mentioned, VP8, VP9 and AV1 all are patent encumbered - they just happen to have licenses that are royalty-free and as someone mentioned, include retaliation clauses which help fighting off submarine patents - but that's essentially a possibly high-stakes game of chicken.

While they are patent-encumbered in the strictest sense of the word, they are not as aggressively licensed as H.266 -- which is what GP was lamenting. Licensing H.266 under the GPL(v3) wouldn't erase the existence of the patents and it would still be "patent-encumbered" in the same sense that VP8/9 and AV1 are. And retaliation clauses are present in basically every free software license that has clauses dealing with…

A big part is in how expensive can you make said retaliation.

I'm more and more fond of calling it all a big game of chicken, a MAD without nukes,

Re: H.266/Versatile Video Coding (VVC)

#116
I'm no expert when it comes to video codecs but I'm surprised that we're still able to see such strong claims of algorithmic improvements to h264, and now to h265. I'm also aware of how patent-encumbered this whole field is and I'm skeptical that this is just a money grab.

This is really just a press release, what's actually new? Can it be implemented efficiently in hardware?

Re: H.266/Versatile Video Coding (VVC)

#117
post #45
post #22

Earlier quoted context omitted.

The dirty secret of video codecs is that you can't make a modern video codec that isn't patent encumbered, which in turn makes it so that even if they wanted to be open, they go for defensive patents, which in turn perpetuate the situation. At least the patent licenses usually used with MPEG mean that private use of open source implementations is free.

> The dirty secret of video codecs is that you can't make a modern video codec that isn't patent encumbered The existence of Theora, VP8, VP9, and now AV1 seems to contradict that theory. You could argue that they infringe on some unknown patents, but that is also arguably true of patent cabals like MPEG (you just hope that the cabal is big enough that there aren't any patentholders lurking outside). The only differe…

Yeah. It's a mess.

The video patents aren't just "patent troll" patents, either. They are highly enforceable, and were registered by corporations like Ampex.

I have been trying to write a simple app to stream RTSP (security cameras), and that has been a pain.

I need to basically use either proprietary (paid) or GPL software to do it.

Video software is not for the faint of heart. Much as I grouse about the licensing, I am not about to develop my own codec.

I did write this one app, which is an ffmpeg wrapper, to convert RTSP to HLS (Which is not -currently- suitable for realtime streaming): https://github.com/RiftValleySoftware/RVS_MediaServer

It's GPL, because I need to use the GPL ffmpeg H.264 codec.

Re: H.266/Versatile Video Coding (VVC)

#119
post #89
post #13

Earlier quoted context omitted.

If one trusted numbers like this, and followed a chain of en vogue codecs back through history, you'd expect that a modern codec would produce files sizes like 3% of MPEG-2 on the same input data. It's all spin. I'm sure it does better, but I'm equally sure it'll turn out to be an incremental benefit in practice. > I wonder how many more CPU instructions are required per second of decoded video compared to HEVC. CPU…

MPEG-2 doesn't support video larger than 1920x1152, so it's hard to compare on 4k video, let alone 8k. But according to https://www.researchgate.net/publication/321412719_Subjectiv... H.265 can achieve similar visual quality with 10% of the bit rate of MPEG-2 even on SD video (832*480). [Edit: not 720p]

832x480 is ~480p video (720x480 is standard widescreen dvd) 720p is 1280x720

Re: H.266/Versatile Video Coding (VVC)

#120
post #99

Shouldn't deep learning based video codecs take over dedicated hardware video decoders as more tensor cores become available in all new hardware? NVIDIA's DLSS 2.0 supersampling is already moving into that direction.

Instead of a video file or stream, that would be more like shipping a program that recreates the video. It might be cool, but it's not really feasible to play back that kind of thing on normal TV hardware.

I'm not sure what you mean. There are already multiple research articles that show that deep neural network based video compression can be competitive, here's an example:

https://papers.nips.cc/paper/9127-deep-generative-video-comp...

Post reply on HN