| ▲ | vkaku 9 hours ago |
| We all know these aren't purely technical reasons, it's to break the monopoly of one Internet Company's decoder format portfolio. You can't let one Fruit Company's format be the thing either, so it's basically a L for engineering but a W for pleasing everyone TBF. |
|
| ▲ | computerbuster 9 hours ago | parent | next [-] |
| AVIF is royalty-free, with open-source implementations not developed by Google. Google's implementation is libaom; as you can see, SVT-AV1 beats it. SVT-AV1 is developed by a number of companies – historically Meta, Netflix, Intel, independent contractors, and others. I worked on SVT-AV1 myself. I don't see how this is a bad thing for everyone, even if Google drove standardization of AV1? |
| |
| ▲ | derf_ 8 hours ago | parent [-] | | There were something like 40 companies involved in AV1 standardization. Quite a few technical contributions did not come from Google, and quite a few of Google's proposals were substantially modified by feedback from others before they were included (and not all of them were eventually included). Source: I lead Mozilla's technical contributions to AV1. | | |
| ▲ | juliobbv 4 hours ago | parent [-] | | It saddens me to see discourse on the internet about AV1's ancestry being focused on Google's VPx line of contributions, while diminishing those coming from Daala (entropy coder...) and Thor (QMs...), as well as inter-company collaborations (CDEF). A redeeming outcome is that with AVIF's new image tuning modes (both in libaom and SVT-AV1), Gianni and I managed to utilize as many AV1 coding tools as possible, including QMs that sorely needed a well-deserved spotlight. Also, thanks for paving the way to the current state of multimedia compression! I'm a longtime fan of Xiph(ophorus) since the 1.0 beta/RC Vorbis days. We used your image sets a lot during our testing. |
|
|
|
| ▲ | throw0101a 8 hours ago | parent | prev [-] |
| > You can't let one Fruit Company's format be the thing either, so it's basically a L for engineering but a W for pleasing everyone TBF. What exactly is "Fruit Company's format"? |
| |
| ▲ | BenjiWiebe 8 hours ago | parent [-] | | I'm guessing HEIC. | | |
| ▲ | Gigachad 6 hours ago | parent [-] | | HEIF isn't an Apple owned format, most modern cameras have it as an option alongside JPEG now. The situation is JPEG is woefully outdated, lacking in HDR support and dated compression. HEIF is technically much better but patent encumbered. JPEG-XL offers all the benefits of HEIF and more, while not being patent encumbered. |
|
|