Don’t use JPEG-XR on the Web

Re:Don’t use JPEG-XR on the Web by Avamander on Monday December 31, 2018 @10:38AM (#18794922)

I don't like WebP because it's either it or HW accelerated browsing - latter I like a tad more because it saves me a bit of battery juice on my laptop.

[ Parent | on HN ]

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 ]

Re:Don’t use JPEG-XR on the Web by TazeTSchnitzel on Monday December 31, 2018 @12:05PM (#18795473)

There's the same problem with Google insisting on VP8/9 for YouTube in Chrome. If your Mac only supports h.264 in hardware you'll get better battery life in Safari.

[ Parent | on HN ]

Re:Don’t use JPEG-XR on the Web by acdha on Monday December 31, 2018 @04:31PM (#18797166)

They also try it in Firefox but fortunately you can disable webm/webp in about:config and get better battery life and image quality.

[ Parent | on HN ]

Re:Don’t use JPEG-XR on the Web by vosper on Monday December 31, 2018 @12:32PM (#18795665)

There's a Chrome extension that forces YouTube to stream h.264

https://chrome.google.com/webstore/detail/h264ify/aleakchihd...

[ Parent | on HN ]

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

Obviously it is a problem with Apple, not Google. People should just push it more to do the job.

[ Parent | on HN ]

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

I don't think Google are free of responsibility. They are prioritising their lower bandwidth over the user's better power usage.

[ Parent | on HN ]

Re:Don’t use JPEG-XR on the Web by vetinari on Tuesday January 01, 2019 @08:53AM (#18800168)

Apple has a bigger share of the blame. They purposely ignore any codec that is outside of their favorites, even if the hardware they ship does support it (i.e. Intel) or doesn't need any hardware support (Vorbis, Flac). On the other hand, they are quick to support any codec, that is problematic to implement elsewhere.

[ Parent | on HN ]