Live data from Hacker News

Google added HEVC support in Chrome

bitmovin.com

141–150 of 225 posts

Re: Google added HEVC support in Chrome

#141
post #11

Doesn't seem to work for me, running chrome 107 on macos and the example does not load for me.

That's why Firefox don't want to support it. Because you can only provide hardware decode unless you pay huge amounts of license fees to the license leeches. Which will make this format only works on some devices but not others.

The h264 has a free software decoder so your browser can play it no matter your device supports it or not

Re: Google added HEVC support in Chrome

#142
post #37
post #15

Every new software and hardware is moving towards the royalty free, agile and efficient AV1 codec. But out of nowhere and 9 years after its release, they add support to the mother of all royalties HEVC codec. Probably had some kind of deal to benefit their android partner Samsung, since they own pretty much most of HEVC patents. https://en.wikipedia.org/wiki/High_Efficiency_Video_Coding#P...

I could be that apple added hevc and heif to their phones (I noticed this long ago when an older iphone wouldn't show imessage images directly from newer phones that were sending images in heif)

I could be that apple added hevc and heif to their phones

Apple made a big deal about HEVC and HEIF starting in 2017. It’s been integrated into macOS, iOS and tvOS since then.

The Camera app on iOS has defaulted to storing photos in HEIF since 2017 or 2018.

High Efficiency Image File Format—https://developer.apple.com/wwdc17/513

HEVC Video with Alpha.—https://developer.apple.com/wwdc19/506

Create image processing apps powered by Apple Silicon—https://developer.apple.com/wwdc21/10153

Re: Google added HEVC support in Chrome

#143

Earlier quoted context omitted.

I think it's remarkable that the pirate scene has barely touched VP9 or AV1. We discussed this 2.5 years ago, nothing really has changed except there's more H.265 than before. https://news.ycombinator.com/item?id=19362098

I remember maybe ten years ago "real" pirates (from "the scene") thought that everything needed to be in rar format, and anything else was considered "p2p" and not as pure. They were also late with h264 and used xvid for far too long.

[deleted]

Re: Google added HEVC support in Chrome

#144
post #123

Earlier quoted context omitted.

I think it's remarkable that the pirate scene has barely touched VP9 or AV1. We discussed this 2.5 years ago, nothing really has changed except there's more H.265 than before. https://news.ycombinator.com/item?id=19362098

Probably all comes down to ffmpeg not supporting av1 well. Pretty much everyone uses ffmpeg or a wrapper around ffmpeg like handbrake to encode. And my understanding is that ffmpeg implements an old and very slow and partially broken version of av1.

ffmpeg can also be built to link to libaom, and my package manager (Macports) does this by default. (Likewise, I think ffmpeg has its own H.264 and H.265 implementations, but also links to libx264 and libx265.) Does it really matter what ffmpeg's built-in implementation is like?

Re: Google added HEVC support in Chrome

#145
post #10

On one hand, that's great for anyone watching HEVC content in Chrome. On the other, I'd prefer to not see further adoption of HEVC and instead see increased deployment of VP9 and AV1 wherever possible. Let MPEG-LA and the other HEVC patent pools+holders... well I'll leave the rest to your imagination. Future looking, no one should even touch VVC/H.266. Unfortunately the above rant does not address the gap in hardware…

Add the hardware support, then we can talk about dropping the proprietary ones. There's no way the costs of royalties, no matter how they indirectly affect me as a user, outweigh the cost of my CPU chugging to handle unoptimized video.

Re: Google added HEVC support in Chrome

#146

Why do pirates prefer hevc over AV1? I assume they don’t care about intellectual property so I assume it comes down to technical quality of the algorithms? Maybe they have moved to av1 and I just don’t know it. Either way the quality of the piracy scene has always seemed vastly better than legitimate channels, up until Netflix.

I don't get how IP factors in here. As a non-pirate just distributing my cooking tutorial, I don't have to pay when I encode in HEVC.

Re: Google added HEVC support in Chrome

#147
post #10

On one hand, that's great for anyone watching HEVC content in Chrome. On the other, I'd prefer to not see further adoption of HEVC and instead see increased deployment of VP9 and AV1 wherever possible. Let MPEG-LA and the other HEVC patent pools+holders... well I'll leave the rest to your imagination. Future looking, no one should even touch VVC/H.266. Unfortunately the above rant does not address the gap in hardware…

I think it's remarkable that the pirate scene has barely touched VP9 or AV1. We discussed this 2.5 years ago, nothing really has changed except there's more H.265 than before. https://news.ycombinator.com/item?id=19362098

I think the biggest reason is lack of hardware decoding, Lots of people have a device that can hardware decode H.265, which is extremely important for 4k content, my x230 really struggled with software 4k decoding of H.265, so I assume the same issue will happen with VP9 and AV1 especially with higher res content.

Re: Google added HEVC support in Chrome

#148

Earlier quoted context omitted.

I remember maybe ten years ago "real" pirates (from "the scene") thought that everything needed to be in rar format, and anything else was considered "p2p" and not as pure. They were also late with h264 and used xvid for far too long.

Jeez, I remember most pirated video was using xvid, what a dark time that was.

xvid in 8 .part files you download separately from putlocker or megaupload, each is zipped with a password you have to find on a phpBB-based forum

Re: Google added HEVC support in Chrome

#149
post #10

On one hand, that's great for anyone watching HEVC content in Chrome. On the other, I'd prefer to not see further adoption of HEVC and instead see increased deployment of VP9 and AV1 wherever possible. Let MPEG-LA and the other HEVC patent pools+holders... well I'll leave the rest to your imagination. Future looking, no one should even touch VVC/H.266. Unfortunately the above rant does not address the gap in hardware…

HEVC is in the VP9 generation of codecs. https://bitmovin.com/vp9-vs-hevc-h265/

Many SoCs support hardware acceleration for VP9 decoding. http://wiki.webmproject.org/hardware/socs

Re: Google added HEVC support in Chrome

#150
post #6

Why is this being done, when AV1 exists? It's hard to see HEVC as anything else than a legal liability.

From https://www.dignited.com/93186/av1-vs-hevc/:

Compared to HEVC, AV1 is still relatively new hence it suffers limited hardware support. Again it is key to note that Intel, AMD, Nvidia, Qualcomm, and most hardware manufacturers already had support for the incumbent HEVC. That means that a hardware accelerated encoder can run HEVC 5x faster than AV1.

And…

A vast majority of devices in the market; phones, TVs, tablets, cameras, browsers, professional-grade applications, etc come with a built-in ability to decode HEVC. Even those coming from the founding fathers of the AV1 codec have added support for HEVC.

Post reply on HN