Thread 107091697

You think webp is bad? Think again.

>>107091697 (OP)
AVIF is capable of high fidelity thoughbeit. Webp is not due to old 8-bit 4:2:0 limitation.

>>107091697 (OP)
AVIF is actually pretty nice.

>>107092270
Too bad google in its infinite jeet wisdom decided 2 things:

A) Mobile devices must have hardware accelerated AVIF decoding to decode AVIF
B) Android 14+ devices are not required to come with said hardware accelerated AVIF decoding chips

>"You can't use Dav1d because... You just can't okay!?"

AVIF is currently the only lossy native HDR still-image format that's actually somewhat adopted, however slightly. JXL was murdered, PNG got retroactive support but it's either choppy bandy 8-bit ugliness or fuckyuge 16-bit memory-hog bullshit that's 70MB for an 8k image. JPG has gainmaps which, while better than 16-bit lossless PNG, is still far more expensive than native 10-bit. There's also native HDR JPG with an ICC v4.4 profile that can encode HDR data but it suffers the same issues that 8-bit PNG has, notable banding and quantization errors galore, not to mention that the ICC profiles for such a format are extraordinarily rare and hard to find. Ironically, places that would normally strip gainmap/HDR metadata sometimes preserve ICC profiles, so you can sneak in HDR images to places that don't normally have them, like Twitter (4chan is not such a place. Thanks, gookmoot, you fag)

>>107092682
>Ironically, places that would normally strip gainmap/HDR metadata sometimes preserve ICC profiles, so you can sneak in HDR images to places that don't normally have them, like Twitter (4chan is not such a place. Thanks, gookmoot, you fag)
Blame cumg. 99.999% of twitter users have shit for brains so they probably don't even know what image metadata even is and thus dox themselves unknowingly on a daily basis.

>>107092682
>JXL was murdered

Not quite, Apple saved it.

>>107093195
AFAIK there isn't a push to include hardware accelerated JXL decoding like there is with AVIF and until that changes the future for JXL looks pretty grim.

Like it doesn't really matter on full blown computers but phones are only like 10% as powerful so they kinda need hardware acceleration for modern image formats.

>>107093253
daiz, it's too easy to find your posts because you keep mentioning hardware acceleration. Nobody cares about that shit, modern cpus are fast enough to decode JXL already.
And PDF just adopted JXL as an officially supported format so every device that wants to claim it supports pdf has to decode JXL now

>>107093309
Yes, modern COMPUTER CPUs. Phone CPUs for very obvious reasons are only like 10% as powerful.

Please keep in mind that what's not shown in pic related is JPG decoding at 100+ megapixels per second. Which explains why Webp adoption is doing so poorly even a decade after it was released.

>>107093349
Normally, I'd never post in a thread like this, I was just scrolling past it, when I saw that image... Galaxy S10e? You know we are in 2025, almost 2026, right? Who cares to the low end flagship from 2019? I mean, nice phone and all, had one, loved the size, but, how is it relevant now? Of course it is underpowered and lacks support for shit, Samsung dropped it years ago, you are killing your own argument there.

https://aomedia.org/blog%20posts/AVIF-at-Five-Powering-a-Faster-Sharper-Web-Experience/

As work on the next generation codec progresses, the working group is laying groundwork for AVIF version 2.0, which will integrate future codec improvements and respond to community needs. “One of the group’s primary goals is to make the next version of AVIF fully equipped for future use cases — especially with the next generation codec,” Podborski said. “We’re asking: How do we expand metadata support and improve alignment with related standards for media packaging and delivery? We’re looking at the features web developers really want, so AVIF stays the best choice for modern image workflows.”

AVIF WON WITH AV2 COMPRESSION

FAGGOT OP BTFO

>>107093685
Like 99% of apps work just fine on A11 and A12 will still be usable for like another decade at least.

>upgradable to Android 12, One UI 4.1
https://www.gsmarena.com/samsung_galaxy_s10e-9537.php

You're completely missing the point DOUGH. Phone CPUs are VERY weak compared to full blown desktop computer CPUs so whether you like it or not they essentially NEED the hardware decoding crutch.

Yeah maybe the iphone 20 pro max elite deluxe super gay edition, only $1,999 + tip can decode JXL at 100+ megapixels per second. What about the affordable stuff that can't? Should they just go kick rocks?

>>107093685
>Galaxy S10e? You know we are in 2025, almost 2026, right? Who cares to the low end flagship from 2019?
Only retards buy new phones yearly. I'm still on my Galaxy S7. Before that I was on Lumia 800 for like 2020. Shit just worked, had no reason to change.

>>107093789
>android 12, OneUI 4.1
We are on OneUI 8.5, can't you see the difference?
A Intel i5 2th gen is also totally usable anon, let's stop progressing, why get new, better stuff, if we can use a C2D, right?
A Snapdragon 8 Elite gen 5 is way better than any consumer grade shit from 5 years ago, phone CPUs run one "app/task" at a time, the 10ms extra you'd take to decode JXL makes no difference at all in the end of the day

>100mp p/ second
Go back to memeing anon, that's no real use case, why would anyone be decoding 100mp/s, especially on a phone?

>>107091697 (OP)
I don't think webp is bad. It's better than j*g.

>>107093852
>yearly
>mentions using a device from 2011 for 9 years, even without any proper support, and insists using a 6 years old device, also without support, is the sane common option
I got it now, you are poor, sorry anon, you can have my old Galaxy S22, stop crying please

>>107093930
It's a fucking phone, I use it to make calls, listen to mp3s, maybe sometimes use it for photos if I have to. If it can't do that then I'll get a new one. And not the $2000 flagship garbage either that becomes obsolete in a year.

>I got it now, you are poor, sorry anon
the reason I'm not poor is because I don't waste money on garbage.

>>107093974
See? That was my first argument, you killed your own argument using that S10e as example, what's the use case? There's no use case, you use your phone for calls, messages and music, software decoding for jxl makes no difference at all even for you, who is complaining about it.

>>107094029
I didn't argue about the S10, I was arguing that only retards buy new phones all the time. Stop wasting your money on garbage.

>>107094067
Oh, I don't change phones that often, I use a iPhone 12 Mini, but I don't care about the extra fraction of a second my phone takes to decode anything

>>107093899
Waste of dubs. Basically everyone is very happen if an image decides in LESS than 1 seconds.

100MP/s by JPG = 4-8 MP images load in less than 0.1 seconds
10MP/s by JXL = 0.4-.0.8 MP images load in less than 0.1 seconds.

I'm almost certain phones built today take images of resolutions higher than 0.4 megapixels...

>>107094097
case in point your faggy faggot 9001 phone uses hardware acceleration for HEIC, the diseased carcass of an image format punked out by none other than "Where's my fucking money?!" mpeg-la.