Don’t use JPEG-XR on the Web

Re:Don’t use JPEG-XR on the Web by RBO2 on Monday December 31, 2018 @01:20PM (#18796015)

HEIF (based on HEVC and support on MacOS/iOS + Android + Windows) is already way better than JPEG. It also provides HW acceleration.

HEIF is made by MPEG. HEIG is extensible (see AVIF fusing the AV1 royalty-free codec). Also an application format (MIAF) will ensure interoperability.

While waiting for native browser support, some js implementation would do the job.

What else?

[ Parent | on HN ]

Re:Don’t use JPEG-XR on the Web by xvilka on Monday December 31, 2018 @10:06PM (#18798673)

Isn't it a patented algorithm? So it is practically useless.

[ Parent | on HN ]

Re:Don’t use JPEG-XR on the Web by RBO2 on Tuesday January 01, 2019 @09:12AM (#18800237)

I agree with you but hey JPEG also had its own patent issues (https://en.wikipedia.org/wiki/JPEG#Patent_issues).

[ Parent | on HN ]

Re:Don’t use JPEG-XR on the Web by zokier on Monday December 31, 2018 @03:02PM (#18796611)

> HEIF (based on HEVC and support on MacOS/iOS + Android + Windows) is already way better than JPEG. It also provides HW acceleration.

Formats do not provide HW acceleration, implementations do. And so far there is zero HW accelerated HEIF implementations for the web.

[ Parent | on HN ]

Re:Don’t use JPEG-XR on the Web by jsjohnst on Monday December 31, 2018 @03:58PM (#18796976)

> And so far there is zero HW accelerated HEIF implementations for the web.

You sure of that? Apple[1] and Qualcomm[2] might argue otherwise.

[1] https://developer.apple.com/videos/play/wwdc2017/513/

[2] https://techreport.com/news/34306/qualcomm-snapdragon-855-sp...

[ Parent | on HN ]

Re:Don’t use JPEG-XR on the Web by RBO2 on Tuesday January 01, 2019 @09:17AM (#18800257)

I don't know who downvoted you but you're correct. The point is that most devices embed an HEVC hardware decoder.

[ Parent | on HN ]