5 ms·
Thanks! Fraunhofer HHI has already released vvenc ages ago: https://github.com/fraunhoferhhi/vvenc https://github.com/fraunhoferhhi/vvenc and it's _really_ good
by Fador 4y ago
Thanks!
Fraunhofer HHI has already released vvenc ages ago: https://github.com/fraunhoferhhi/vvenc https://github.com/fraunhoferhhi/vvenc and it's _really_ good on compression performance as well as speed.
The difference is that we used our own HEVC encoder as the base whereas Fraunhofer (and most likely x265 team) use the reference encoder VTM: https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM https://vcgit.hhi.fraunhofer.de/jvet/VVCSoftware_VTM giving them all the tools from the beginning.
We are aware of the problems with HEVC and VVC, and it's sad to find out that the VVC licensing terms are even worse for open-source...
- ksec 4y ago>and it's sad to find out that the VVC licensing terms are even worse for open-source... What and why is that ?
- Fador 4y agoAccording to what I've read, MPEG LA would also charge the some fees for "free software". It makes me wonder if e.g. ffmpeg would adopt VVC would they have to pay for it? https://www.streamingmedia.com/Articles/ReadArticle.aspx?ArticleID=151163 https://www.streamingmedia.com/Articles/ReadArticle.aspx?Art...
- ksec 4y agoI see what you mean. It probably wouldn't matter if a user is compiling from source and not downloading the binaries. It is also unfortunate the terms couldn't be simpler. It seems most internet companies in the west ( dominated by US ) are not going to use VVC, while India, China and Japan are all ready to jump on the VVC tech. Broadcasting has shown interest in VVC as well.