News for hackers. Stuff that matters.
Re:Google Quietly Added HEVC Support in Chrome by Thaxll on Tuesday October 25, 2022 @08:06PM (#33337936)
Did you tried to encode anything with av1? Even with a high end CPU it's just not feasible, I tried with ffmpeg and it was encoding a single digit fps per seconds.

A video of just 10min would take many hours, on the other end h265 encoding is slow but doable.

Re:Google Quietly Added HEVC Support in Chrome by varenc on Tuesday October 25, 2022 @08:11PM (#33337981)
Try compiling ffmpeg with `--enable-librav1e` and use the `rav1e` encoder implementation. It's supposed to be the fastest software encoder, though of course it can still quite slow depending on the settings.

If you have a newish Intel CPU they're supposed to have good AV1 hardware encoding support. See SVT-AV1. (which ffmpeg also supports: https://trac.ffmpeg.org/wiki/Encode/AV1#SVT-AV1 )

Re:Google Quietly Added HEVC Support in Chrome by camkego on Tuesday October 25, 2022 @08:34PM (#33338160)
I don't think there are CPUs with integrated GPUs from Intel that do AV1 encoding yet. Raptor Lake launched on October 20, 2022, and while RL will decode AV1, it won't encode it. The Intel Arc cards will encode AV1. The next generation of Intel CPUs with integrated GPUs are supposed to have AV1 encode. Maybe a year or two away?
Re:Google Quietly Added HEVC Support in Chrome by xfalcox on Tuesday October 25, 2022 @11:43PM (#33339571)
By next month, every current gen discrete GPU will hardware encode AV1, be it Intel Arc, Nvidia 4XXX or AMD 7XXX.
Re:Google Quietly Added HEVC Support in Chrome by nabakin on Tuesday October 25, 2022 @11:14PM (#33339391)
Intel CPUs don't have AV1 hardware encoding support quite yet. Their latest 13th gen CPUs have AV1 hardware decoding support though. The recent performance improvements[1][2] are for software encoding.

[1] https://www.phoronix.com/news/AOM-AV1-3.5

[2] https://www.phoronix.com/news/SVT-AV1-1.3

Re:Google Quietly Added HEVC Support in Chrome by LinAGKar on Wednesday October 26, 2022 @02:15AM (#33340377)
But does that get the same quality? All the codec performance comparisons I've seen have totally ignored the video quality, making the utterly meaningless.
Re:Google Quietly Added HEVC Support in Chrome by i80and on Tuesday October 25, 2022 @08:09PM (#33337964)
For what it's worth, Intel & Netflix's AV1 encoder SVT-AV1 is extremely fast -- it changed my mind about what encoder rates are possible with AV1, to the point that I'm very happy with realtime CPU encoding.
Re:Google Quietly Added HEVC Support in Chrome by Thaxll on Tuesday October 25, 2022 @08:11PM (#33337985)
I will try that because libaom was really slow.
Re:Google Quietly Added HEVC Support in Chrome by nirbheek on Wednesday October 26, 2022 @08:04AM (#33342432)
libaom is the 'reference' encoder, it is built for correctness, not speed. rav1e and SVT-AV1 are built for speed.
Re:Google Quietly Added HEVC Support in Chrome by andsoitis on Tuesday October 25, 2022 @09:13PM (#33338464)
> Netflix's AV1 encoder SVT-AV1 is extremely fast

https://netflixtechblog.com/svt-av1-an-open-source-av1-encod...

Re:Google Quietly Added HEVC Support in Chrome by slabity on Tuesday October 25, 2022 @08:17PM (#33338042)
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.

Re:Google Quietly Added HEVC Support in Chrome by ComputerGuru on Tuesday October 25, 2022 @08:26PM (#33338108)
You haven’t mentioned at what fps you can encode.
Re:Google Quietly Added HEVC Support in Chrome by NavinF on Tuesday October 25, 2022 @08:44PM (#33338248)
Last sentence implies he can encode at 30fps, same frame rate as the video.
Re:Google Quietly Added HEVC Support in Chrome by Thaxll on Tuesday October 25, 2022 @08:49PM (#33338302)
I highly doubt that, my 5800x can't encode at that speed with h264 ( slow preset ) so a modern codec is probably 10x slower.
Re:Google Quietly Added HEVC Support in Chrome by alrlroipsp on Tuesday October 25, 2022 @10:24PM (#33339006)
Cool guess, cowboy
Re:Google Quietly Added HEVC Support in Chrome by dkh on Tuesday October 25, 2022 @08:55PM (#33338349)
This was also true of H.265 in its early days before there was widespread support. I once had to wrangle a few workstations to act as a renderfarm overnight in order to transcode a couple hours of footage by the next morning having not been aware that we were dealing with H.265 until the day before it had to be done.

But also yes, as others are pointing out, this is a problem rapidly being addressed and is not atypical for new media formats.

Re:Google Quietly Added HEVC Support in Chrome by sorenjan on Tuesday October 25, 2022 @09:47PM (#33338713)
SVT-AV1 is as fast or faster than x265 for me on my 10+ year old CPU, at least when using high (fast) presets.

Here's a guide with some various options for using it with ffmpeg: https://gitlab.com/AOMediaCodec/SVT-AV1/-/blob/master/Docs/F...

Re:Google Quietly Added HEVC Support in Chrome by prvc on Tuesday October 25, 2022 @11:08PM (#33339349)
With the correct encoder and settings, it can be faster to encode than x265, for any given "efficiency" that x265 can achieve. Of course, the efficiency can be pushed higher than that, too, still with a reasonable encoding time.
Re:Google Quietly Added HEVC Support in Chrome by awill on Tuesday October 25, 2022 @11:49PM (#33339601)
exactly. vp9 isn't actually that good. It's clearly worse than hevc. AV1 is better, but there's limited hardware encoding/decoding support. The result is exactly as expected.
Re:Google Quietly Added HEVC Support in Chrome by Dylan16807 on Wednesday October 26, 2022 @12:20AM (#33339775)
https://people.videolan.org/~unlord/SVT-AV1_BD-rate.png

This picture is a little old now but it should get across the point of why libaom isn't a meaningful speed test.

It can be set to go faster, but the default speed is only one notch faster than on this chart.