Thread 105901583

WHY IS EVERY IMAGE ON GOOGLE IMAGES FUCKING AVIF
AIIIIEEEEEEE

>>105901583 (OP)
they are?
that's fucking based
still not using google though

>>105901583 (OP)
WHERE ARE MY JPEG-XL PICTURES GOOGLEBRO

>>105901608
Too good to be in use. Yahweh said so 2000 years ago in desert or something.

>>105901583 (OP)
What's wrong with AVIF?

>>105901583 (OP)
>I finally add a 'webp to png' converter to my right click menu
>everything changes to AVIF
there is a global conspiracy to oppress and annoy me. well, probably not.

I don't mind new formats as long as they have universal and recursive support
webp can't be opened by most image editors, and has fucked colors when viewed in the image viewer, so by principle, it has no right to be deployed

and it doesn't help that modern browsers forcibly convert jpgs/jpegs to webp, EVEN WHEN THE SERVER DOESN'T SERVE WEBPS which is always the smartass thing people respond with ("hurr blame websites for having them")

>>105902971
>and it doesn't help that modern browsers forcibly convert jpgs/jpegs to webp, EVEN WHEN THE SERVER DOESN'T SERVE WEBPS which is always the smartass thing people respond with ("hurr blame websites for having them")
Jesse, what the fuck are you talking about? No browser does this. CDNs do. Fucking retard.

>>105902994
then how come navigating to a url that ends in .jpg will result in .webp in say Edge, but .jpg in Waterfox? if it happens on a CDN level, it should be universal for everyone

AVIF unlike Webp already has hardware acceleration so this might actually be a really good replacement for JPG. The problem with formats like JPEG-XL is they're extremely slow and painful to decode compared to hardware accelerated AVIF. Anything that takes longer than say 0.1 seconds to load will drive normies nuts.

>[5.1/H-1-17] MUST have at least 1 hardware image decoder supporting AVIF Baseline Profile.

https://source.android.com/docs/compatibility/14/android-14-cdd

>>105902971
AVIF should be more universal since it's going to get hardware acceleration but the bad news as far as I know is you have to not only make sure you buy an Android 14 phone or later but also make sure it wasn't upgraded from an earlier version of Android.

Not sure how this is going to pan out on wankblows/macfaggot computers, they could botch this whole thing up by not having AVIF hardware acceleration.

>>105901583 (OP)
> avif
Never heard of it.
Your browser is supposed to advertise what images you support and web sites provide it.

>>105903612
Probably because your old janky machine lacks hardware acceleration for it.

Why didn't they name it something that rolls of the tongue easier?? AV-IFF? This is no good!

>>105903463
>If Handheld device implementations return android.os.Build.VERSION_CODES.U for android.os.Build.VERSION_CODES.MEDIA_PERFORMANCE_CLASS, then they:

Nothing ever happens.

>>105904121
Like I said in the post after that this only applies to "new" Android 14 phones. Which to be fair is going to be confusing for the average joe.

Anyway the important thing is because of this hardware acceleration people will begin taking pictures and screenshots in the .avif format down the line which would help JPG in general be replaced. CDNs can only do so much compared to billions of humans uploading billions of .avif images.

>>105901601
>>105901583 (OP)
is 4chan flooded with retarded newfags (notice the re**it ty*ing and corporate bootlicking) or is this a samefagging shill?

>>105903463
Put your trip code on, Daiz aka pixdaiz, ss2, jonsneeders, fixlives, etc.

>hardware decoding

You forgot to mention Tel Avif doesn't support more than x4000 pixels, has no progressive mode, is missing anything expected of a modern image, and isn't even a real image format because it loops a video frame infinitely.

I haven't seen you mention hardware decoding in your Tel Avif shilling in a long time.

Why are you doing it again?

Remember when you posted a benchmark that showed Tel Avif is a thousand times slower than JPG because you thought it showed it's a thousand times faster? You fucking subhuman.

>>105903612
it's a shitty video codec pretending to be an image format and is full of backdoors (malware), hence why Google and rest of the corporate world are shoving it down everyone's throat.

>>105905040
>Still implicating me
I already posted. There is no trip code to turn on.

>>105904224
Android 14, with the aforementioned return flag, with eligible AV1 decoding profiles (WebP tier slop).
Not looking too bright at the moment.

>>105903463
>Anything that takes longer than say 0.1 seconds to load will drive normies nuts.
normies sat for a fucking decade through combined thousands of years of gta online loading screens

>>105905352
Yeah and now they're used to things loading instantly, grandfather. It's almost like there's an expectations for technology to get better and not worse.

>>105905040
>>105905326
You don't need much to outperform JPG especially the sea of JPGs that have NOT been encoded with jpegli.

Will a 1488-bit AVIF look nicer? Yeah, no duh but the one that can be hardware accelerated will load in 0.0001 seconds on a modern toaster so yeah.

Reminder Daiz has only posted one real benchmark and it was by mistake because he thought it showed JPG was a thousand times slower than Tel Avif

Literal subhuman

>>105903027
Probably because your freetard browser can't display webp files dumbass

>>105905401
the average cattle willingly bathes in ads and notifications on every website and "app" they use
they are incapable of discerning anything let alone a 100ms delay

>>105905455
You're confusing me with some one else. See the post above you. AFAIK hardware accelerated AVIF i still much better than Webp and the only thing that can really compete with Webp is jpegli.

>>105903027
URL doesn't mean shit. The server will serve whatever it wants and however it wants, and as long as there's a correct mime-type and file header the browser will display it just fine. Some browsers tell servers that they don't support webp (even if they actually do), and some servers respect that, hence the different behavior between fox-likes and webkit-likes. But in general, the server makes the final decision. And usually that decision is "whatever costs us less in traffic charges".

>>105905560
>You're confusing me with some one else.

That's exactly how it works, Daiz.

You being a piece of shit aka a shill have zero reason to samefag.

>>105905679
You can inspect the files yourself in that benchmark. If I were some kind of shill I would just post random images with nothing to back them up.

I mean if you're claiming that hardware accelerated AVIF is worse than Webp then isn't it fair to provide some proof for this claim?

>Please download my cherry picked shit that's likely infested with viruses
>This proves I'm not Daiz

So right, Daiz.

>>105905779
This IS an anime board, is it not? Or did reddit buy 4chan?

>>105905040
>what paranoid schizophrenia does to a motherfucker
fucking anti-tripfags are just as bad as the actual tripfags

>Look mommy
>I said reddit bad
>Despite Reddit being a pedo site and their users making up the majority on 4chan
>This means everyone must buy all of my retarded propaganda

You're a genius, Daiz.

why bother with it when we already have PNG

whatever. wake me up when chromium supports jpeg-xl.

>>105905868
I don't even know who he's talking about, I just downloaded >>105905434 and post it around because it seems legit, like the files inside are webp/jpg when you upload them to an exif website. I don't even know much about image encoding other than using squoosh lol.

But from my limited understanding OG JPG just blows hard. jpegli is supposed to "Make JPG great again! (tm)" but who knows if this thing will really take off.

>>105905064
> video codec like avi full of malware
That actually makes sense then. Thanks.

>the """daiz""" schizo is back
lol. how the hell did a codec obsessed random mindrape someone THIS hard?

>>105905064
>>105906271
>jpeg-xl v0.3.2 is affected by a heap buffer overflow in /lib/jxl/coeff_order.cc ReadPermutation. When decoding a malicous jxl file using djxl, an attacker can trigger arbitrary code execution or a denial of service.

https://app.opencve.io/cve/CVE-2021-28026

So which perfect image format should we use then? Obviously it's not Jpeg XL.

>>105906376
Makes me feel better knowing someone out there has less of a life than me desu. I have no friends irl but at least I don't spend 90% of my waking life foaming at the mouth when someone talks bad about jpeg xl.

>>105906415
indeed. cheers to whoever they are.

>>105906388
I don’t know what one to use, but I’m pretty sure .GIF is no longer encumbered by unisys, and has has all the bugs worked out of it by now, so I’ll use that.
It’s probably yet another ploy to get you to upgrade your browser to get more binary blobs and kernel services (hi chrome!) on your PC.

>>105906457
>>105906415
>>105906376
slit your throat instead of samefagging, daiz

>>105907506
meds.

>>105905455
Daiz is a subhuman. He's behind every single Tel Avif and WebPiss shill post. You can pinpoint the exact moment he activated his bot by sifting through the earliest threads about image formats.

https://desuarchive.org/g/thread/103683062/#103683766
https://desuarchive.org/g/thread/104401598/#104401644
https://desuarchive.org/g/thread/104590870/#104592380
https://desuarchive.org/_/search/text/chatgpt%20powershell/username/ss2/
https://desuarchive.org/g/thread/104519200/#104519200
https://desuarchive.org/_/search/text/4chan/username/ss2/

>>105907602
daiz won.

if u won, why are you spamming the website with retarded propaganda to get gookmoot to support your tranny codecs?

>>105907602
>You can pinpoint the exact moment he activated his bot by sifting through the earliest threads about image formats.

It was when he found out Apple added support for the new JPG. He hates anything that Apple adds support for.

>>105908547
Should we really be supporting apple though? Isn't the ceo like a literal cock sucker and not just a metaphorical one?

Also why are you even bumping this shit ass thread if it makes this mad? What do you gain by feeding the troll?

>>105903463
>AVIF unlike Webp already has hardware acceleration so this might actually be a really good replacement for JPG
8tb is like what, 40 bucks now? why are you autists needing to swap to a whole nother image format to save 40kb per image

>>105908643
Depends on the resolution but that's not what hardware acceleration is for. On the contrary hardware acceleration is BAD if you want the smallest file size possible.

The real purpose is better battery life and faster encode/decode speeds. If you look at decoding speeds you'll clearly see that without hardware acceleration AVIF is not a good replacement for JPG yet and only because decode speeds suck.

>>105905670
Chrome requests .webp in it's headers and there's no easy to disable it that I know of outside of manually editing the request headers with an extension (lol).

>>105908694
Man it's almost like using old shit ass codecs from ww2 is costing people money...

>>105908586
apple supports eating food

when are you going to starve yourself to show us that you're not a faggot?

>>105909129
webp is not the answer and google forcing it is AIDS

https://youtu.be/w7vXJbLhTyI

>>105911127
I don't get the purpose of these tests. Lossy to lossy compression is bad and should be avoided as much as possible. Anyway I think it's fair to point out that webp could become obsolete if jpegli adoption becomes popular enough, see >>105905434

Otherwise you still get a pretty huge boost in compression efficiency over libjpeg-turbo.

>>105911127
Also I just noticed this but jpegli is made by... google? I'm not sure what they hope to gain by sabotaging their existing webp image format desu.

https://www.cnx-software.com/2024/04/05/googles-jpegli-open-source-library-can-compress-high-quality-images-35-more-than-traditional-jpeg-codecs/

>>105908681
>The real purpose is better battery life
I've lost count of the times i've replied to this bullshit you keep repeating with this graph... and you never seem to address it, weird...

>>105908586
Apple breathes air. Are you going to stop doing that to show us you don't support Apple, Daiz?

>Also why are you even bumping this shit ass thread if it makes this mad? What do you gain by feeding the troll?

That makes no sense because trannies can pick any other "rule violation" for the public bsn reason. Why are you trying to get people to admit breaking a certain rule?

Also, every single time this thread gets bumped, which is you doing it, is when the thread is about to die.

>>105911248
Also, you're a retard.

Google doesn't create anything.

They throw money at random projects so they can then seize them and have JEWSA say they've got."ownership" of them, and say "we can't be a monopoly because of this".

If JPGXL was easier than WebPiss or Tel Avif for transfering viruses, Google would've killed the tranny codecs and added JPGXL.to Chrome.

>>105911279
Can you post a modern one with avif hardware acceleration? I don't get why decoding an AVIF through software would use less power than decoding a webp, which should be easier to decode.

>>105903640
>he still pretends that av1 hardware decoders are currently already being used to hardware accelerate avif image decoding
this to me is the most insane part of your retardation
we've already discussed this, you have no proof that this is happening, no browser currently does this AND NEVER WILL
webp has been around since 2013, most phones and lots of mobile/desktop gpus have vp8 hardware decoding, yet it's never used to decode webp images, shut the fuck up.

>>105911314
Why do you talk like that?

>>105908681
nice graph, daiz. i bet google didn't create it and didn't use a buggy jpg decoder because there's no way google is a bad faith actor like you.

>>105911324
>[5.1/H-1-17] MUST have at least 1 hardware image decoder supporting AVIF Baseline Profile.

https://source.android.com/docs/compatibility/14/android-14-cdd

>>105911332
why did you resume spamming hardware decoding, daiz?

>>105911334
Not him but it seems legit. Decoding jpeg xl images causes my PC to freeze for like 2 seconds.

>>105911348
try using a decoder that isn't outdated

>>105911279
>lost count of the times i've replied to this bullshit you keep repeating
Yea he does that, it's like talking to a bot. He stopped using his tripcode(s?) after the hack for some reason. It's a shame because this is a very interesting topic that doesn't get the attention (I think) it deserves but dunning-kruger try hard fags like this shut off any decent discussion that could be had.

>>105911366
I tried using the latest jpegview and nomacs. Anything high res and jpeg xl will just trash my computer.

>>105911395
You honestly sound like daiz pretending to not be daiz. Are you just advertising yourself like a whore? What are you even selling anyway?

>>105911339
>android now requires phones to have an avif hardware decoder, that means it's currently being already used to decode images in browsers
very big logical fallacy here, the fact that a decoder is present or even mandated doesn't mean it's getting used or that it will ever be
and this also only applies to phones
so how exactly does that respond to what I said? oh yeah as always, it fucking doesn't, kill yourself.

>>105911169
The point is images get recompressed/modified in a variety of ways depending on what service they're uploaded to or used on.

It's not odd for something like a meme to get saved and reuploaded over and over by individuals sharing it to each other.

>>105911395
^ yeah this
I've lost count of the times I was having some good video/image codec related discussion with some other anon and this fucking retard comes in spamming his usual unrelated copypasta bullshit posts ruining the whole bread
just so fucking annoying

>>105911429
There was never a webp image hardware decoder you disingenuous KIKE. VP8 was limited to like 1080p and webp images can be like 32k res.

Anyway we now DO have the dedicated image hardware decoders for IMAGES encoded in AVIF and not just fucking static stills of AV1 video. HUGE difference since go can tile AVIF images higher than 4K res (like say 100MP) and still have them be hardware decoded.

>>105911460
except you were always implying that av1 decoding was the same as avif decoding, moving the goalposts it seems
well that doesn't change the fact that
1. most devices don't have an avif decoder and never will
2. the presence of an avif decoder doesn't mean it will get used whenever possible
3. all of this is bullshit anyways because Qualcomm is still releasing SoCs which don't even have av1 decoding for brand new android 15/16 smartphones just fine, in fact, I have yet to see an SoC that claims to provide an avif decoder, do you have an example? I bet you can't find one, retard.

>>105911499
Stop drinking the "daiz" kool-aid, maybe this thread is being discussed by multiple individuals and not just you and this "daiz" boogeyman that lives rent free in your head.

I DON'T KNOW IF AVIF HARDWARE ACCELERATION WILL BE USED FOR WEB BROWSERS.

I just know that it's there now which didn't happen for webp.

>>105902719
sounds like some lispy jew

>>105908694
Correct
>>105902994
Edit your request headers

>>105902971
>>105903027
Edit your request headers, retard
>>105912618
Correct

>>105912625
Fuck it I'm going to sleep
>>105908694
Correct.