logoalt Hacker News

fishgoesblubyesterday at 7:28 PM6 repliesview on HN

Of the 3 software AV1 encoders, the only one that is fully dead is the Rust encoder (rav1e). If people truly wanted memory safe encoders/decoders, they would fund and develop them.


Replies

datakingtoday at 9:45 AM

https://github.com/memorysafety/rav1d got funded and developed. it is unfortunately a bit slower (typically by a single-digit percentage) than dav1d.

Sesse__today at 10:47 AM

I can totally understand why people would want a memory-safe decoder, but a memory-safe encoder is niche. Finding a memory-safety bug in a decoder is a matter of finding a single unchecked integer field somewhere; finding a memory-safety bug in an encoder requires first finding some sort of logic bug in the encoder and then crafting an adversarial input that survives a number of highly lossy transformations.

Compare the number of CVEs against x264 (included decoders don't count!) and FFmpeg's H.264 decoder.

simonaskyesterday at 10:53 PM

Encoding is a way, way less risky thing to be doing compared to decoding.

vlovich123yesterday at 8:08 PM

Fully dead in what sense? Seems like it still has active development to me.

show 1 reply
snvzztoday at 9:48 AM

There are many paths to memory safety, even if the one Rust project seems to be going nowhere.

There's other memory-safe languages, and there's formal verification.

e.g. seL4 favors pancake.

essephyesterday at 7:31 PM

> If people truly wanted memory safe encoders/decoders

Really? How many codecs have your neighbors contributed money for the development of, just curious.

show 2 replies