News for hackers. Stuff that matters.
Re:Dav2d by 0x1ceb00da on Sunday May 31, 2026 @09:38AM (#48345583)
What does "complexity" mean here? Computation required?
Re:Dav2d by WD-42 on Sunday May 31, 2026 @11:53AM (#48346725)
dav1d is the av1 decoder and it’s an insane feat of engineering. Written in assembly, it even eschews the normal c calling convention to get even better performance.
Re:Dav2d by IshKebab on Sunday May 31, 2026 @12:29PM (#48347046)
The normal C calling convention is really only for cross-binary calls (e.g. between shared libraries). If you're not doing that you can ignore it; it's not a weird thing to do. It would be odd to strictly follow it in assembly and I assume compilers don't either.
Re:Dav2d by adgjlsfhk1 on Sunday May 31, 2026 @07:58PM (#48351075)
Unfortunately, in absence of inlining, compilers mostly respect calling convention even when they don't have to.
Re:Dav2d by BillStrong on Sunday May 31, 2026 @10:07AM (#48345806)
Yes, much higher computation required to encode it, and decode it, both.
Re:Dav2d by Caspy7 on Sunday May 31, 2026 @11:21AM (#48346420)
He only mentioned decode complexity. Would be interesting to know the average encode complexity compared to AV1.
Re:Dav2d by kiicia on Sunday May 31, 2026 @03:16PM (#48348752)
Encoding speed even on Mac Studio is atrocious, it’s in range of single frames per second as opposed to realtime+ for even h265
Re:Dav2d by F3nd0 on Sunday May 31, 2026 @04:07PM (#48349253)
The specification for AV2 has only been finalised very recently, so performant encoders have not yet been developed. Meaningful comparison to older codecs like H265 and AV1 will only be possible once that has changed. (It'll be slower, but almost certainly not one-frame-per-second slow.)
Re:Dav2d by Dylan16807 on Monday June 01, 2026 @08:24AM (#48355901)
Getting the full bitrate gains will be slower.

For any specific bitrate and quality target, there's a good chance it'll be faster.

Re:Dav2d by simjnd on Sunday May 31, 2026 @09:50AM (#48345670)
Yes