>>104432922
>Bullshit otherwise single pass CRF would have been functional day #1 when VP9 was released way back in 2013. It took jewgle over a decade to fix that motherfucker.
Because TrueMotion's codecs NEVER had fucking working rate control. They probably backported it from fucking libaom.

x265's CRF rate control HAS NOTHING TO DO WITH PATENTS, IT WAS JUST IMPLEMENTED BY MORE COMPETENT DEVS. IT WAS PURE INCOMPETENCE AND "USECASE FOR NOT JUST DOING A 2-PASS VBR ENCODE (with equally shitty rate control) BECAUSE WE ONLY WANT THIS IP FOR A PATENT-FREE YOUTUBE CODEC?"

Guess what happened when most of the active devs stopped contributing to x265? Jeet slop, breaking commits, etc.

Back | Go to board

Board:

/g/

Thread:

libvpx-vp9