Live data from Hacker News

Google added HEVC support in Chrome

bitmovin.com

81–90 of 225 posts

Re: Google added HEVC support in Chrome

#81
post #31

What's the point? No one is using it on the Web and if anyone will try to use it commercially, they'll be eaten by patent trolls like MPEG-LA. Google might afford shelling out money to those trolls to add it to the browser, but not everyone is Google. So it's basically DOA. Did anything change about that recently? > Great feature, but where is the necessary hype!? There is surely no need for any hype for dead end tec…

[deleted]

Re: Google added HEVC support in Chrome

#83
post #64

Earlier quoted context omitted.

I'm able to encode using av1an (which I believe still uses ffmpeg as its backend) at 3440x1440@30Hz with 10bit color using a mid/high-range AMD 3800X processor. I'm not sure what might be wrong on your end, but it sounds like ffmpeg's default configs might not be well-optimized yet if you can't encode in real time.

You haven’t mentioned at what fps you can encode.

Last sentence implies he can encode at 30fps, same frame rate as the video.

Re: Google added HEVC support in Chrome

#84

Earlier quoted context omitted.

> The mystery is who is paying whom ? Hardware IP people are paying licenser people, with consumers eventually paying hardware IP people. > "Why use HEVC(pay) when AV1 exists ?" Because HEVC has hardware support, right now, so it's faster. > "Why care about AV1 if everyone is paying ?" People don't much.

>Because HEVC has hardware support, right now, so it's faster. Most new hardware supports hardware decode for AV1 too. There were 1-2 generations prior to the current one that had HECV but not AV1, but that sample size will become irrelevant over time. >People don't much. Well, clearly people who make decisions do. If you ask an average person on the street if they care about HEVC or AV1, they don't. If you ask Netfl…

PS5, XBox One, Chromecast, iPhone, iPad, AppleTV support HEVC but not AV1.

And they represent a significant proportion of video consumption devices.

Re: Google added HEVC support in Chrome

#85
post #66
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…

It's ironic, not one week ago there were a bunch of complaints on this site saying that Google was abusing their position of power (controlling YouTube, Chrome, Android TV, etc) by pushing AV1. Now they bring HEVC support to Chrome and the top comment is another complaint! (That said, I agree with you. I think a codec being royalty free is a very good reason to prefer it to other codecs.)

There may be more than one person posting on HN.

Re: Google added HEVC support in Chrome

#86
post #14
post #6

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

Most older hardware has HEVC decoding but only the last few gens have AV1. My 10980XE is like 96% occupied while watching AV1 without HW acceleration so many smaller devices can't do anything resembling a smooth playback.

> My 10980XE is like 96% occupied while watching AV1 without HW acceleration

That seems high. What resolution and frame rate is the video? And which decoder are you using? dav1d is a highly optimized software decoder so that's the one to try:

https://code.videolan.org/videolan/dav1d/

It's used in Firefox, Chrome, ffmpeg, etc.

Re: Google added HEVC support in Chrome

#87
post #66
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…

It's ironic, not one week ago there were a bunch of complaints on this site saying that Google was abusing their position of power (controlling YouTube, Chrome, Android TV, etc) by pushing AV1. Now they bring HEVC support to Chrome and the top comment is another complaint! (That said, I agree with you. I think a codec being royalty free is a very good reason to prefer it to other codecs.)

> Now they bring HEVC support to Chrome and the top comment is another complaint!

Well, you know how it is, some complaints are wrong and some are right.

Re: Google added HEVC support in Chrome

#88
post #71
post #65

Earlier quoted context omitted.

That applies for TV show. For movies though, the vast majority of new torrents are Blurays re-encoded to HEVC (x265 being the encoder used pretty much every time).

UHD Blu rays are also HEVC.

well yes, but not everyone wants to download 70GB movies, so blu-ray movies are often re-encoded for smaller filesizes (10-20GB 4K HEVC, 5-10GB 1080p H264 AC3 sound, 1-5GB 1080p HEVC AAC)

Re: Google added HEVC support in Chrome

#90
post #83

Earlier quoted context omitted.

You haven’t mentioned at what fps you can encode.

Last sentence implies he can encode at 30fps, same frame rate as the video.

I highly doubt that, my 5800x can't encode at that speed with h264 ( slow preset ) so a modern codec is probably 10x slower.
Post reply on HN