anons I have always wanted to learn about shit like multimedia codecs and containers but never got the hang of it. always getting bogged down by a bazillion different acronym. so if you will please do the needful and help me get started with it

The OP is one of Daiz's bots that runs on some LLM. All it does is spam and schizopost by lying pathologically, playing the victim and samefagging (same as what Daiz does).

https://desuarchive.org/g/thread/105932881/#105932999

>>107586843
If all things go as intended you will only have to worry AVIF/AV1/and Opus.

>>107586928
What do you think of the new captcha?

>>107586759
why is there so much drama about image formats which are almost equally good

>>107586759
h.264 is perfection

>>107587005
IMHO I think it's because modern ones practically speaking need hardware decoding, which is what AVIF is now getting. Otherwise the benefits aren't really worth it over JPG.

File: pixDAIZ is here.webm (94 KB, 360x270)

94 KB WEBM

>>107586759
kys

I prefer JpegXL. It's comfy.

File: 1761851345769498.jpg (8 KB, 241x209)

8 KB JPG

>>107586928
>>107587103
>>107587141
You're the actual legit daiz(tm) aren't you? Mad nobody really remembers you because you're a tranny now?

File: ︂attachment.png (1.52 MB, 643x643)

1.52 MB PNG

>>107586759
Why would I encode images as VP9 when I can do this?

File: AVIF_BASELINE.png (57 KB, 1280x720)

57 KB PNG

Sorry I forgot to post this after my thread but picrel are AVIF HW decode limits. It's currently only present in phones/tablets that came with Android 15, everything else seems to be limited to decoding a max resolution of 1920x1080 sadly. Tiling will extend the max resolution further but there isn't an automatic grid derivation option in avifenc yet and image viewers probably can't properly decode high-res tiled AVIF images yet anyway.

Beside effectively being capped to ~9 megapixel images AVIF HW can only handle 4:2:0 at 8 or 10 bit color precision. The good news is that the --sharpyuv avifenc setting seems to be working incredibly well for some images. So much that I'm able to achieve visually lossless quality similar to a quality 95 4:4:4 JPG. It doesn't work on all images but when it does it's wild since 75% of all color information is missing yet somehow AVIF is able to regenerate it to the point where you can't even notice...

>>107587417
Because 4chan does not support APNG yet lol. It's not a static image webm like my webp2 thread, it's an actual microsoft powerpoint slideshow, just wait man...

>>107586943
AVIF is good for anime images but JXL is better for photos

File: 1_starfish.png (759 KB, 1024x1024)

759 KB PNG

Also here is the image I'm currently testing with.

>>107587437
This was true before the high IQ tune. Now AVIF is ~90% as good as JXL in photographic images. I'll post a comparison of that in an hour or so, look forward to that.

File: out.webm (1.59 MB, 1280x1024)

1.59 MB WEBM

See if you can subjectively rate the AVIF as inferior quality to the quality 95 JPG. They both scored SS2 90 and are both technically visually lossless. Which normally shouldn't be possible because again 75% of all color information is missing.

>90 = visually lossless. Distortion not noticeable by an average observer in a flicker test at 1:1 from a normal viewing distance. This corresponds to the typical output of cjxl -d 0.5 / -q 95 or libjpeg-turbo 4:4:4 quality 95.

https://github.com/cloudinary/ssimulacra2

File: jpg.jpg (382 KB, 1024x1024)

382 KB JPG

If you don't trust my lossless RGB VP9 webm slideshow, here are the raw files themselves to compare against the source >>107587454

Picrel is quality 95 4:4:4 JPG and here is the AVIF: https://files.catbox.moe/rspnzc.avif

What's more wild is the filesize, at 136KB, the AVIF is about 60% smaller than the 353 KB JPG. I expected like maybe 20% smaller desu...

do you feel in charge?

File: ︂openbased.org slash 4chan.png (2.81 MB, 877x877)

2.81 MB PNG

I miss the days when we could bambooze 4chan by modifying WebM track headers to insert AV1 and Opus streams that could only be played in Firefox, MPV, and VLC. The ole embed wars.

File: ︂lurkmoar.png (3.98 MB, 1600x900)

3.98 MB PNG

>>107587909

File: 1laura.png (3.01 MB, 1024x1024)

3.01 MB PNG

I've decided on this photographic image, it has plenty of camera noise JXL shills love to jerk about all the time.

File: out.webm (3.19 MB, 1280x512)

3.19 MB WEBM

Had to crop the comparison by 50% to maintain lossless in RGB VP9. Files and settings used will be included as well in case I fucked something up. All images scored SS2 80 and while not visually lossless, are still very high quality.

>80 = very high quality. Distortion not noticeable by an average observer in a side-by-side comparison at 1:1 from a normal viewing distance. This corresponds to the typical output of cjxl -d 1.5 / -q 85 or libjpeg-turbo 4:2:2 quality 85.

https://github.com/cloudinary/ssimulacra2


File size: 254 KB (~29% smaller than JPG)
https://files.catbox.moe/ptvr88.avif
--sharpyuv -s 6 -q 72 -d 10 -y 420 --cicp 1/13/1 -a tune=iq

File size: 284 KB (~20% smaller than JPG)
https://files.catbox.moe/isrw29.jxl
-q 91 -e 7 --override_bitdepth=10

I'm not sure why AVIF won here desu. On average you'll see JXL achieve 10% smaller file size vs AVIF in photographic images not the other way around LOL.

File: 4jpg.jpg (357 KB, 1024x1024)

357 KB JPG

Here's the bloated JPG.

File: no-good.webm (41 KB, 1056x720)

41 KB WEBM

The AVIF animations are going to be a headache if you want to really replace GIF desu. You can't just feed avifenc 420 Y4M files since the --sharpyuv preprocessing won't work and if you feed it 444 Y4M then it overrides -y 420. The only way that I think you export a high quality animation properly is if you screenshot individual video frames and splice them together later. However the only way to get 4:4:4 video from 4:2:0 video is if you zoom it to 50%.

File: 1740586324979241.png (1.66 MB, 1086x1586)

1.66 MB PNG

Does anyone know if grain synthesis is supported by avif hardware decoding? That should help deal with the hipster faggot grain thing.

So which is better for when I make a pretty picture and want to save it at whatever quality is default on the Save File interface?
Like what every normal person doesñ

>>107588458
Probably not. Baseline spec is pretty... baseline.

>>107588832
Depends on the picture but if the CLI scares you, you can try squoosh defaults and choose the one you like the most. Hopefully the kind of settings used here become the default for pretty GUIs soon.

>>107586759
>For Images:

avifenc --sharpyuv -d 10 -y 420 -q 70 --cicp 1/13/1 -a tune=iq in.png out.avif

I simply use

convert input.png output.avif

Am I missing out on avif image quality?

did she get rid of the starfish?

>>107589411
Yes, the new image quality tune uses special quantization matrixes that do more than smear pixels.

>>107591711
cool then. Will try that

File: the future.jpg (109 KB, 1080x903)

109 KB JPG

What causes this and don't say homosexuality

>>107592999
What I posted isn't a normal YUV 420 VP9 webm, its lossless RGB VP9 without any chroma subsampling otherwise it would be pointless for image comparisons. I'll assume you're using some dying browser like firefox which doesn't support lossless RGB VP9

>>107593076
>shills telavif
>shills chromium
k daiz, don't care, still using jxl and firefox.

>>107593365
also btw actually it works fine for me on firefox, idk what that retard's problem is.

>>107586759
>static comic loses resolution to compression artifacts as pointless video plays
dropped

File: computer.webm (55 KB, 960x720)

55 KB WEBM

>>107593365
Thanks for the bump? Are you technically inclined at all or do you just like calling everyone daiz? Maybe you could help me with this: I'm trying somehow import video frames to a --sharpyuv -y 420 animation avif file (so it can be hardware decoded and emulate RGB output of GIF) but there's no easy way to do this and 4:4:4 Y4M overrides -y 420.

My clunky setup is going to be taking a screenshot of individual video frames to save as PNG, resizing them by 50% to get 4:4:4 output, and then somehow feeding that to avifenc...

>>107593415
LOLnope, this is a lossless RGB VP9 webm, it's just that JPG truly is that awful for anime images. I triple checked, mediainfo gives me this (before and after upload):

Video
ID                             : 1
Format                         : VP9
Format profile                 : 1
Codec ID                       : V_VP9
Duration                       : 14 s 999 ms
Bit rate                       : 1 944 kb/s
Width                          : 1 050 pixels
Original width                 : 24 580 pixels
Height                         : 1 080 pixels
Original height                : 33 346 pixels
Display aspect ratio           : 0.972
Frame rate mode                : Constant
Frame rate                     : 6.000 FPS
Color space                    : RGB
Bit depth                      : 8 bits
Bits/(Pixel*Frame)             : 0.286
Stream size                    : 3.48 MiB (96%)
Default                        : Yes
Forced                         : No
Color range                    : Full
Color primaries                : BT.709
Transfer characteristics       : sRGB/sYCC
Matrix coefficients            : Identity

File: Start_doing_this.jpg (53 KB, 1024x576)

53 KB JPG

The 4chan team should start using AVIF / WEBP for thumbnails. If they did, they would save money on their server bill and have money left over for fixing the site.

>>107593475
>they should start using avif/webp to replace the 2 kb jpeg thumbnails rather than support webp/avif for uploads and making jpeg transcodes/higher quality thumbs for the few users running browsers/clients without webp/avif support
what a retarded idea

>>107593527
>the few users running browsers/clients without webp/avif support
You can't post from a browser without webp support.
>support webp/avif for uploads
They should also do that.

>>107593579
>you can't lurk on 4chan
???

>>107593614
Realistically who is using a browser without webp support to lurk 4chan? Autists, maybe.

File: StatCounter-android_versi(...).png (153 KB, 1280x720)

153 KB PNG

>>107593579
Webp maybe but AVIF is dead on arrival without hardware decoding support. Only 25% of phones/tablets now have Android 15 which is pretty terrible desu.

JPEG-XL WON

reminder mods don't touch daiz as he gives them access to drawings of cheese pizzas on fakku for free, hence why daiz never gets banned despite breaking all their rules.

>>107593651
>Only 25% of phones/tablets now have Android 15 which is pretty terrible desu.
and how many of those SHIPPED with a15? it's like <5%.
(of course none of this even matters because hardware decoding support isn't actually required no matter how much you pretend it is)
it's incredible how i keep telling you the same stuff over and over but you never learn anything, kys.
of course, conveniently, you will never look into how much faster jxl (losslessly transcoded from legacy jpeg) is at decode speed (6x faster than regular native jxl).

>>107593470
i can see the artifact in the video nerd. fuck what your data says. you are a faggot. im so mad at your retarded ass

File: pathetic.webm (27 KB, 1056x720)

27 KB WEBM

>>107593895
Practically it is otherwise it would have NEVER been a requirement at least for phones that shipped with A15. The truth is phone CPUs just aren't that powerful as they don't violate laws of conservation.

Computing performance = power consumption. You're not going to get i9-14900K performance out of a phone.

File: image codec phone battery(...).png (5 KB, 866x487)

5 KB PNG

>>107594003
>phone cpus don't violate laws of conservation, but phone antennas do.
sure, let's keep repeating the same nonsense over and over, that'll get us somewhere eventually, i'm sure of it...

>>107588079
It may come as a surprise for you but most images worth:

1. archiving
2. delving into encoding autism

are not chroma subsampled sisterfucker anime screenshots. Pictures are best left untouched in their original format or losslessly compressed. Every time you perform lossy-to-lossy compression, a kitty gets ripped in half by a gorilla.

File: out.webm (1.3 MB, 960x540)

1.3 MB WEBM

Okay, I think I mostly figured out how to automate the screenshots to 50% PNGs (to get 4:4:4) and then feed that to avifenc. I have a breedy gud animation sequence to work with but instead of spamming the 10 individual frames here I'll just post a lossless RGB VP9 webm instead. Extracting the PNG files is simple just ffmpeg -i in.webm %02d.png on the CLI. Also unfortunately the High IQ tune does not work with animations, the variance aq mode works at least.

@echo off & setlocal EnableDelayedExpansion
set avif_anim=--sharpyuv -d 10 -y 420 -q 70 --cicp 1/13/1 -a aq-mode=1 --fps 20
mkdir png_444 & for %%f in (*.png) do ffmpeg -hide_banner -i "%%f" -vf scale=iw/2:ih/2 -y "png_444/%%~nf.png"
for %%F in (png_444\*.png) do set files=!files! "%%~nxF"
cd png_444 & avifenc %avif_anim% %files% "../out.avif"

https://files.catbox.moe/gbidfc.avif

Filesize: 64 KB (95% smaller)
VMAF: 92.6

>>107594067
Don't feel like dragging this on too much but I'd love to know why you think the engineers who mandated AVIF hardware accelerated decoding on phones that ship with A15 are fucking brainless retards who eat shit from their hands. Are you really certain phones are capable of i9-14900K performance and hardware accelerated decoding is a huge mistake? Because there's going to be millions of those things soon...

>>107594085
delusional

LMFAO the GIF is bigger than the lossless RGB VP9. Amusingly it did score VMAF 96

I guess the next step is to increase the animated AVIF quality until it hits VMAF 96...

File: out.gif (2.28 MB, 960x540)

2.28 MB GIF

fuck forgot GIF

Filesize: 2.28 MB (75% bigger lol)

File: 1766083257670894-ezgif.co(...).gif (378 KB, 960x540)

378 KB GIF

>>107594193
fixed

>>107594209
VMAF: 78

Could you perhaps up the quality to at least VMAF 92.6 as the 64KB AVIF?

File: 1766083257670894-ezgif.co(...).gif (87 KB, 427x240)

87 KB GIF

>>107594223
What are you using this gif for anyway? As a reaction image? If so, I'd scale the gif down to 240p.

File: Untitled.png (66 KB, 946x603)

66 KB PNG

>>107594246
No, I'm trying to compare the compression efficiency of the lossless RGB file here >>107594125

To GIF and animated AVIF because the assumption is the latter will be like 80-90% more efficient but comparing objective quality is very hard because I just realized VMAF doesn't work with RGB...

Fuck, so I guess I have to convert that AVIF back to a lossless RGB VP9 webm and do a proper SS1 comparison with that...

File: avif_to_rgb-vp9.webm (720 KB, 960x540)

720 KB WEBM

>ffmpeg does not yet support animated AVIF yet
FUUUCK, I don't like using avifdec...

I had to rename all the 0.00000000x files to 01.png... and packed it back to a lossless RGB VP9 webm.

File: Untitled2.png (65 KB, 946x603)

65 KB PNG

PSNR and VMAF now work and RGB to RGB SS1 says...

The 2.28 MB GIF is INFERIOR in quality to the 64 KB animated AVIF. Over 95% smaller file size and better quality.

>get banned for """racism""" for mentioning daiz's recent name for his bot
>the bot itself never gets banned

trannies are so thirsty for cheese pizzas.

>>107594629
Why would you brag about ban evading?

why did you take off your trip code to gloat about being an untouchable for giving cheese pizzas to trannies, daiz?

>>107594125
>I'd love to know why you think the engineers who mandated AVIF hardware accelerated decoding on phones that ship with A15 are fucking brainless retards who eat shit from their hands.
let's repeat the answer to this question for the dozenth time these last 6 months:
...because there's a difference between "it's better" and "it's mandatory".
why do you think all devices still have hardware decode for h264 (including constrained baseline/baseline profiles which have a completely different feature set from the other heavier profiles and which were literally invented to be easy to decode in software)?
I've often used vp8 for an example of this, it's a codec so fast to decode in software that it was used to deploy youtube on the wii (basically a slightly overclocked gamecube) with no hwdec whatsoever, and do I have to bring up the fact that nvidia is still shipping mpeg-1 hardware decoders on 1500+$ gpus? are you going to make the claim that mpeg-1 is too demanding and wouldn't be feasable to decode in software? "it has hardware decode so it must be strictly necessary" is a huge logical fallacy you keep making with no data to back it up.
also do I have to remind you that avif supports high res animations also? do I have to repeat the concept that almost every device has a jpeg decoder that goes unused 99% of the time and is only used for motion jpeg when you use your webcam? there might be some scenarios where hwdec IS required, but it's not "a bunch of still 1920x1080 pictures on a webpage"
>i9-14900K performance
most pictures on the web are 1080p at best, are you really making the claim that you need a 14900k to decode a 1920x1080 avif reasonably fast? it's insane that you genuinely think all of this stuff, sounds like bait but isn't, you need meds.

>>107586759
nigger, there is already AV2.
AVIF is dead before it ever got popular.
Move on.

File: 1764973856405630.png (30 KB, 471x552)

30 KB PNG

>>107594741
Not him but most low end phones would legitimately struggle to decode a 512x512 AVIF especially if it's 10-bit. Even super premium iPhones (at least before they were made in india) utilize hardware decoding for the cancer that is HEIC.

Sure hardware decoders become redundant over time but AVIF desperately needs them else it will be guaranteed to fall into obscurity like jpeg xl. Unless hardware accelerated decoding also becomes abundant for jpeg xl as well and to be fair that might happen in the next few years...

BUTT as it stands AVIF is now ahead of jpeg xl in that regard and the longer jpeg xl goes without hardware acceleration the more of a meme it will become desu.