JPEG XL

I haven't ever seen `.avf`

Agreed that .jxl is better

<:This:805404376658739230> <:JXL:805850130203934781>

btw if you have nitro you can do this

<a:funkyparrot:730177001733881940><a:funkyparrot:730177001733881940><a:funkyparrot:730177001733881940><a:funkyparrot:730177001733881940><a:funkyparrot:730177001733881940><a:funkyparrot:730177001733881940><a:funkyparrot:730177001733881940><a:funkyparrot:730177001733881940><a:funkyparrot:730177001733881940><a:funkyparrot:730177001733881940><a:funkyparrot:730177001733881940><a:funkyparrot:730177001733881940>

or this

<:SadCat:805389277247701002>

. <a:oop03:759136967530381334><a:oop13:759136664281939999><a:oop23:759136664655626260><a:oop33:759136663560519731> <a:oop02:759136664341184512><a:oop12:759136664886050846><a:oop22:759136665196953601><a:oop32:759136665121456159> <a:oop01:759136665058279475><a:oop11:759136666505314316><a:oop21:759136665880625153><a:oop31:759136665469583401> <a:oop00:759136664898633728><a:oop10:759136665763053599><a:oop20:759136665934626816><a:oop30:759136664487723073>

<a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736><a:jump:729482913665777736>

Should I try to buy nitro and expense it because clearly I need animated emotes to properly discuss JPEG XL with early adopters?

I don't buy it myself, I heard there is something like xbox gift cards that give you 3 moths, that's what I was gifted >clearly I need animated emotes to properly discuss JPEG XL with early adopters? Not only that, at least 10 packs of stickers is required. We don't need to `funny` `haha` `lol` `lmao` `that's make me laugh` you just <:kekw:758892021191934033><:kekw:758892021191934033><:kekw:758892021191934033><:kekw:758892021191934033><:kekw:758892021191934033><:kekw:758892021191934033><:kekw:758892021191934033><:kekw:758892021191934033><:kekw:758892021191934033>

Animated emojis are the number 1 priority of life

<a:catdance:770738257846599710><a:Interpretivedance:681616487709933597>

I just added this animated emoji to the server:

<a:ajxl:806626687130533959>

<:Stonks:806137886726553651>

<@!794205442175402004> as creator, you get to say how "JXL" is officially pronounced, so that people can ignore it and pronounce it differently

I'm going with "Jacksil"

Knowing that they will ignore it... Uh...

There are a lot of options actually

Jay Excel is probably the obvious one

Jixel, rhyming with pixel is nice imo

Some places pronounce J as Y, like in Spanish. *Yuckles*

My name is Jon, not pronounced John but Yon.

YonXL

So Yixel is also an option

Spanish would be more like Hixel, no?

Or ghixel or something

But in British it would be Hache Eck Sell

Chixel

The french can say j'excelle

J'ai Pègue Excelle

and the German pronunciation for ".jxl" would be `Der Gemeinsame Fotoexpertengruppe Extra groß`

`JEXEL`

`G-EX-EL`

~~Why am I adding so many emojis <:ReeCat:806087208678588437>~~

<a:catvibe:752443357413900339> <a:catbop:783085141496561724><a:copycat:484178121080176646><a:catstare:765750672523132998>

Extra groß haha

Wtf is that <:PepeRage:806632585584312360>

<a:PopCat:797931705171836978>

<a:aSCcatVIBING:787353742013497394>

<a:ravecat:750221441689190480>

<:RaysCookie1:713195761508155463><:RaysCookie2:713195761348771862><:RaysCookie3:713195761361485876><:RaysCookie4:713195761575133245><:RaysCookie5:713195761453629492> <:RaysCookie6:713195761696768081><:RaysCookie7:713195762221056072><:RaysCookie8:713195761751293973><:RaysCookie9:713195762061672468><:RaysCookie10:713195761990631504> <:RaysCookie11:713195761688641627><:RaysCookie12:713195761860608041><:RaysCookie13:713195762074517594><:RaysCookie14:713195761915002942><:RaysCookie15:713195761994825748> <:RaysCookie16:713195761613144145><:RaysCookie17:713195761986306088><:RaysCookie18:713195761768202261><:RaysCookie19:713195761873190974><:RaysCookie20:713195761961271317> <:RaysCookie21:713195761973723237><:RaysCookie22:713195761990369300><:RaysCookie23:713195761482858528><:RaysCookie24:713195761873190972><:RaysCookie25:713195761743036456>

Jacksel, Yucksle, Jocksal

The possibilities are endless

Ambiguous pronunciation was a major design goal for this project

We absolutely needed to beat all existing codecs in all aspects

Including GIF

Gif <a:dogescared:749458017954562058>

Huge inefficient ugly noise chonker of a file

So I am proud to announce we have over 9000% more ambiguous pronunciation of the acronym

<:heart100:435854137649922048> GIF

Oh well, for people who have Nitro:

<a:CatYes:806636752952754186><a:CatNo:806636752810409986>

<@!794205442175402004> p_ It is imperative that you include some aspects in the .jxl pronounciation that are only feasible by Dutch (or even Flemish) speakers.

Rijndael set a great example.

Juigksel?

Jijgkstreul

Hmm, gkstr. Not quite as bad as "herfstschraalte", but close.

And for those who want to use `.jxll` for lossless, that one is pronounced "Jouwksloellel"

:D

In romanian it's pronounced simmilar to Yon: Ion

A true achievement, I expect this will boost JXL awareness 300% when someone starts a meme around it

https://tenor.com/view/dragon-ball-z-dbz-vegeta-its-over9000-mad-gif-4474083

I like how jixel sounds. But I always found it stupid for projects to impose their name pronunciation. Also jixel reminds me of Nixie Pixel 🙂

Jixel bells, jixel bells https://c.tenor.com/VprUl6-Kf3YAAAAM/jingle-bells-christmas-sweater.gif

God ,please, don't, don't name it jixel

jijgkstreul it is then

How about.....Gixel? :))

written with a J of course

https://tenor.com/view/tracy-morgan-smh-shake-my-head-hell-no-no-gif-4844098

:)))

Fun fact: when <@!794205442175402004> and I started working on what (much) later became FLIF, I had to pick a name of the repository, so I named it JIF (Jon's Image Format). Some time later, after I had made more contributions, and we started over, we needed a new name, and (not entirely seriously) considered JPEG (Jon & Pieter's Encoding of Graphics).

JPIF was also an option

Right.

https://github.com/sipa/JIF

``` README Initial commit 10 years ago ```

Waaaaaaaat?

....time flies man

https://tenor.com/view/titanic-gif-5101515

My psyche is permanently damaged after I discovered that it's pronounced YON

👴

https://tenor.com/view/the-big-lebowski-thats-like-your-opinion-man-gif-15076479

yep yep

Feel free to mentally pronounce my name John

I don't mind

I get called John Snayeers all the time

I'm guilty too)

jan snierz because we speak in american

maybe correct is yamn/jon snaiers how i call it

@_wb_ I have that problem too. I'm Peter Woolley.

Hi Peter Woolley.

https://tenor.com/view/lol-sheep-cute-dancing-dance-gif-7441326

<a:sheep:624288529614241792>

https://mobile.twitter.com/594E51/status/1353405118050394114

🤣

-My photos are not heavily compressed Their photos:

https://res.cloudinary.com/practicaldev/image/fetch/s--L1bkiw5h--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/arsze4aod9owmia43wzo.jpg

patchs not bad

original

catches a lot, not quite everything yet though. But pretty cool what it can do already 🙂

don't patch on continue line

how to see the vardct blocks?

I think there's a benchmark_xl option for it

you can get it using e.g. `benchmark_xl --input=input.png --codec=jxl:d4 --debug_image_dir=debug_output`

that's the kind of output that gives

(for this input image)

<@179701849576833024> maybe it would be better to use color codes for different block sizes instead of these bitmaps

cool

what is ccs.png?

no idea, will have to check the code for that 🙂

#CoreDev, no doc, see code

it's connected components for patch detection

yeah, I didn't want to bother with finding visually distinct colors 😄

#ff0000 #00ff00 #0000ff #ffff00 #00ffff #ff00ff for the most common ones

oh, discord does not render hex-colors? 😦

also no distinction between blue and cyan emojis

<a:VerifiedYellow:798877413584535552> <a:VerifiedRed:798877099569446922> <a:VerifiedPurple:798874858552557579> <a:VerifiedPink:798876646786334721> <a:VerifiedOrange:798877179588509696>

<a:VerifiedMint:798875001595756577> <a:VerifiedMagenta:798876491264819280> <a:VerifiedLime:798874682757218305> <a:VerifiedGreen:798874798389592086> <a:VerifiedDarkBlue:798876202403233792>

<a:VerifiedCyan:798873653029896203> <a:VerifiedBlue:798875774605197363> <a:VerifiedBlackPink:802462672233824266>

Colors <a:Hypercat:681237365599240216>

Or maybe some gradient based on size, e.g. 🟥 for smaller than 8x8, 🟧 for AFV, 🟨 for 8x8, 🟩 for 16x8, 8x16, 16x16, 🟦 for up to 32x32 and 🟪 for bigger

<a:JojoPls:703040356652154920><a:skelerave:699745220476272740><a:blob:621363689232138276><a:someonesaidgo:539828319873663004><a:partygopher:591403079065272322><a:rainbowRick:431665618840846336><a:rainbowMorty:431663209548611594><a:Dino:594254381613056042><a:agreepink:707983051824562256><a:hypercry:752443564146950204><a:gaysheep:747434587612905612><a:crystal:778373216292306965><a:redS:394231565946716160><a:orangeS:394231611656372225><a:yellowS:394231586406793227><a:greenS:394231548154609668><a:blueS:394231598108639244><a:yeet:545092834492022785>

<a:catdance:770738257846599710>

<a:gems:772901705062154260>

<a:Hypercat:681237365599240216> <a:RicardoRGB:681616487894876170> <a:RGBYoshi:685553600948469760>

https://tenor.com/view/rainbow-puke-puking-rainbows-gif-5293170

<a:CatYes:806636752952754186>

Now I have to rename this channel AGAIN. What is it with you guys

🤷

https://tenor.com/view/the-simpsons-homer-bart-lisa-marge-gif-3722733

https://tenor.com/view/nick-young-question-marks-what-excuse-me-huh-gif-4486363

https://c.tenor.com/Fmdj24JVTHwAAAAM/kittorz.gif

<a:RGBYoshi:685553600948469760><a:RGBYoshi:685553600948469760><a:RGBYoshi:685553600948469760><a:RGBYoshi:685553600948469760><a:RGBYoshi:685553600948469760>

<:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619> <:BlobYay:806132268186861619>

<a:PopCat:797931705171836978><a:PopCat:797931705171836978><a:PopCat:797931705171836978><a:PopCat:797931705171836978><a:PopCat:797931705171836978>

What is this channel anymore

Pure epilepsy

We now have the power to change the channel into anything we want <a:dogeevil:749457940041302078>

I have no idea to be honest.

There are probably better places for this kind of thing.

No

Oh wait, yes

It used to be the off-topic channel

The AV1 server <a:dogeevil:749457940041302078>

Then it became the on-topic channel

And now it is somehow the epilepsy channel

What's next?

#Soviet_takeover

<:salute:747551849694888107>

#uniformly_random

<:RedStar2:763553622768222278><a:military:714292044440403989>

https://c.tenor.com/sRx6btX50RcAAAAM/cow-utter.gif

🥩

https://c.tenor.com/mPA5HGlgaI8AAAAM/bones-thats-so-random.gif

https://c.tenor.com/c5KQmpTEDdoAAAAM/pizza-cowboy.gif

A uniformly random channel

Sounds challenging

<a:pizzaspinpepe:715239197253828688>

To keep it uniform

Or maybe combine with the soviet takeover idea: #uniformed_random

https://c.tenor.com/k_t2I_jjPowAAAAM/seed-zrno.gif

There seems to be a statistically significant correlation between the R, G, and B channels.

<a:VerifiedRed:798877099569446922> <a:VerifiedGreen:798874798389592086> <a:VerifiedDarkBlue:798876202403233792>

<:greenT:394231744380796938><:redT:394231753050423297><:yellowT:394231764849000448><:blueT:394231772017065986><:orangeT:394231780753932297> <a:greenS:394231548154609668><a:redS:394231565946716160><a:yellowS:394231586406793227><a:blueS:394231598108639244><a:orangeS:394231611656372225> <a:greenH:394231654971080704><a:redH:394231667826360321><a:yellowH:394231683550806016><a:blueH:394231701280129034><a:orangeH:394231712248365057>

<a:RaysNut:737691574221406299>

<a:arolloverfox:803080149716566087>

627842432748378803270141867695262118097500640514975588965029300486760520801049 153788541390942453169171998762894127722112946456829486028149318156024967788794 981377721622935943781100444806079767242927624951078415344642915084276452000204 276947069804177583220909702029165734725158290463091035903784297757265172087724 474095226716630600546971638794317119687348468873818665675127929857501636341131 462753049901913564682380432997069577015078933772865803571279091376742080565549

825792630239159000355760903247728133888733917809696660146961503175422675112599 331552967421333630022296490648093458200818106180210022766458040027821333675857 301901137175467276305904435313131903609248909724642792845554991349000518029570 708291905255678188991389962513866231938005361134622429461024895407240485712325 662888893172211643294781619055486805494344103409068071608802822795968695013364 381426825217047287086301013730115523686141690837567574763723976318575703810944 339056456446852418302814810799837691851212720193504404180460472162693944578837 709010597469321972055811407877598977207200968938224930323683051586265728111463 799698313751793762321511125234973430524062210524423435373290565516340666950616 589287821870775679417608071297378133518711793165003315552382248773065344417945 341539520242444970341012087407218810938826816751204229940494817944947273289477 011157413944122845552182842492224065875268917227278060711675404697300803703961 878779669488255561467438439257011582954666135867867189766129731126720007297155 361302750355616781776544228744211472988161480270524380681765357327557860250584 708401320883793281600876908130049249147368251703538221961903901499952349538710 599735114347829233949918793660869230137559636853237380670359114424326856151210 940425958263930167801712866923928323105765885171402021119695706479981403150563 304514156441462316376380990440281625691757648914256971416359843931743327023781

1 2 Fizz 4 Buzz Fizz 7 8 Fizz Buzz 11 Fizz 13 14 FizzBuzz 16 17 Fizz 19 Buzz Fizz 22 23 Fizz Buzz 26 Fizz 28 29 FizzBuzz 31 32 Fizz 34 Buzz Fizz 37 38 Fizz Buzz 41 Fizz 43 44 FizzBuzz 46 47 Fizz 49 Buzz Fizz 52 53 Fizz Buzz 56 Fizz 58 59 FizzBuzz 61 62 Fizz 64 Buzz Fizz 67 68 Fizz Buzz 71 Fizz 73 74 FizzBuzz 76 77 Fizz 79 Buzz Fizz 82 83 Fizz Buzz 86 Fizz 88 89 FizzBuzz 91 92 Fizz 94 Buzz Fizz 97 98 Fizz Buzz

yes

<:majestic_potato:504748474001129482>

<:WhiteFoxSalute:689481667412623385>

even better

You have Nitro?

Yes. It's the old nationally broadcasted version

99999 99999 99999 99999

hmm, listening to the Great USSR Anthem I was thinking....Why not add sound support to JXL too....lossless and loosy? 🤔

maybe the iso bmff format allows that?

since this is uniformly random, I'll make a silly suggestion

just convert the audio into a series of frames and then encode those as jxl

I want jxl images to be self contained chat rooms

So every image can be discussed

one time I compressed a video as a vorbis audio file

Messages sync with blockchain

The most loosy of modes of JXL should just include a text with the description of the image: "This image contains Shrek doing donuts in a orange car"

But why

We do what we must because we can.

It is only bad performance

<@!269796879691153409> Привет

Прив, нашёл на форуме, заодно и тут посмотрю какой движ происходит.

Discord needs a translate button

Может быть, а может быть и нет 👁️ 👃 👁️

!tr en bonjour

😦

Bonjour. Aujourd'hui, on va parler de JPEG-XL, un format d'image de nouvelle génération. Hello. Today, we will be talking about JPEG-XL, a next-generation image codec.

All the 'J's of JXL (Jan, Jon, Jyrki) have the same pronunciation.

Jxl will be called simply jpeg from 99,8 % of people and yixel from a core dev

base

Simply "jpeg"? It would be great if the transition could be smooth enough to not even need a new word, but I doubt it...

opt

trying to find better heuristics for reducing ringing...

which one do you like better?

On phone atm, cannot pixel peep

unprofessionally in the Ikea chair? 😄

😎

To me this is more clean

this is an example of 5 or so recent improvements where I try to reduce ringing and improve JPEG XL on those images where it performs worst in comparison to AVIF

I'm currently working on getting this submitted in our private repo -- from where it will surface likely with 0.3.2 or 0.4

often the individual changes are rather subtle and it is difficult to know if the progress is real or if I'm running in circles 😄

like 7 new artefacts appear but 11 old ones go away

Avif in this image is very good

yes, we are far from AVIF quality with this image

my experience is that the directional filtering gives 2 % density on the average

but on some images it can be 20 %

jpeg xl spends a lot of bits to get the sky right, but no one looks at the sky with this kind of photos

probably next up for me is to mess up the sky some more and get bits to spend on the architecture

I don't want to go all the way where AVIF is with messing up the sky, but there can be some productive middle-ground

Yep, perfect sky but bad structure is only a bad photo

How you can you misure local bit density? Esperience?

that image pair was at d3, here the same with d1

Bigger than 64 block can help?

I usually think which direction I want to go with the heuristics and then apply an optimization algorithm to let simplex search to find out the details

for these improvements the changes would often be in initial quantization and in choosing the integral transforms

Thay image is like the BIKE image, it is basically a demo image for having many directional prediction modes and directional deringing filters. I consider it a best-case situation for such codecs.

choosing the integral transforms is a really nasty problem to deal with if one wants to keep the maximum error down

yes, if we lose on this image bit time it is of not much practical consequence

but it can become a huge PR loss

so I want to mitigate and make it as good as it easily comes

Sure, doesn't hurt to be better also at this

I'm eye-balling a more representative corpus of 50 images for each such change -- checking that we don't throw away the baby with the bathwater

Also for vector-graphics like images, this happens and it is nice to be better at it

based on my current speed of improvements I think I can make these images 10 % better, i.e., similar experience with 10 % less bits

I suspect it will end up 20 % worse than AVIF for these images at low BPP

I tried three different directional approaches during JPEG XL development

none of them worked at high quality

and expensive to encode for

the AVF transform was inspired by oblique boundaries

that is our primitive reflection of directional stuff, but it does work at very high qualities, too

Not that bad for a single case

it is super effective when a boundary hits 1-3 corner pixels of the next block -- and it doesn't spoil the other frequencies like predicting+filtering does

Directional prediction is a kind of vectorization. It is good at low-fidelity, if you don't mind shapes slightly changing because things get rounded to the nearest angle etc. At high-fidelity I suspect it doesn't really help because the residuals don't really have less entropy than the signal itself, if you cannot quantize them away.

Chats look like this almost all the time

Can we get another(cooler) color for early adopters?

Any specific suggestion for a new color?

red-ish orange. maybe. not seeing other roles with red.

some shade of blue)

purple could work too

🟪 or 🔵

that blue is bit too close to core dev role

core dev color could be more intense like this

or just 🔴

Just throwing some examples

that doesn't look v good tbh

General rule is that person in RED can ban you <:cmon:798146744936300556>

So this is how we read the chat now)

Lol, I feel green

<:shrek:789698153053683713>

I'm flamingo

https://youtu.be/6hJv5yBLe9c

<@794205442175402004> you can spam youtube pools with something like "what is your favorite image codec", it is easiest way to stack youtube interactions,which will raise your channel discoverability exponentially

And this is what everyone in youtube game doing atm

What are youtube pools?

*Poll

The image I posted above

Ps. Don't ban <:monkaS:654081051848605726>

I didn't know there were polls on youtube

There is tiktok like videos also

Oh, see who's videos resurfacing))

Dance Your Codec!

I feel satisfied with my color

https://c.tenor.com/n5LbGzoC7U8AAAAM/dancing-cute-baby.gif

I think now a more common and easy to read blue/green for the early adopter (like in AV1) would be ok

This green not good?

I tweaked that saturation you know

Just fine for me(the current one here)

It's a little darker and "blurry"

ask for votes of colors then convert them to XYB, average there, and then convert back 😄

<:GreenPotion:585609317097537536>

Does ryomivasalama mean anything?

Is it Finish?

I made this account for my chess activities and accidentally use it for JPEG XL 😄

salama is blitz/lightining

ryomiva is crawling

because I like to play fast games (15 second to 5 min), but I often run out of time

and yes, it is Finnish

I'll probably change it soon to my real name 'Jyrki Alakuijala' to reduce confusion

I think a regular green would be better for reading, as in the AV1 screenshot (this will not be a problem now since dev has more aggressive colors)

let's copy the AV1 green 😄 no shame in doing that

I'm going to experiment with larger transforms -- if expressing some large relatively homogeneous patches with some more error (less fidelity) would free bits for more appropriate use

i.e., less bits (=fidelity) to the sky/lake/snow/etc, more to the edges and other high contrast things

Unusual colors are not a problem for some rare roles, but for people with a lot of activity (early adopter), it is better to choose more readable and usual colors AV1 - JXL

Too saturated now

Or ok?

Now it's too bright

better

way too saturated

but colors are better

Ok toned it down a bit

maybe the yellow

It's good now

use same color as the crown

if you can

I don't want that crown

ok good

How can I remove it?

I didn't know that this is a thing in image compression development -- to find the label colors for groups

It is crucial

ahah

It is a matter of utmost importance

we could consider finding a balanced set of points in a psychovisual colorspace such as XYB by using iterative algorithms

Reminds me of JPEG picking a color for its new AI activities

Exactly, let the AI pick it's own color.

Yep, I hope moderation, chatting and answering the simplest questions in this discord will not distract from the further JXL development <:Thonk:805904896879493180>

I think they are not very careful with the colorspace selection for the logo color selection, I was disappointed by the lack of rigor used in the logo color selection >:-D

(not really!)

would be perhaps cool if there was a inter-format between the encoders (HEIF, AVIF, WebP2, JXL) to be able to use the block splitting algorithm results in another encoder

It's acid green

👩‍🔬

Block splitting constraints are quite different in each codec though

https://support.discord.com/hc/en-us/articles/360000516572-Server-Ownership-The-Crown-Icon

Aha

Got rid of that throne

I mean crown

One of us

https://c.tenor.com/-MTAOUsKfuoAAAAM/freaks-one-of-us.gif

👑

https://tenor.com/view/austin-powers-i-love-gold-goldmember-gif-19735343

Jon I of JPEG XL

https://c.tenor.com/bbiUNmTXamkAAAAM/the-office-toby-hating.gif

<a:gold:775147514084851752>

https://c.tenor.com/jYQeNYk_AjkAAAAM/life-of-brian.gif

https://tenor.com/view/he-is-the-messiah-monty-gif-19570851

https://c.tenor.com/HzQPE7fENwoAAAAM/bright-side-bright-side-of-life.gif

You guys are in serious violation of the uniformity directive.

Right.

https://c.tenor.com/NICVMIw0YvMAAAAM/turtle-ride.gif

And that's how I learned discord doesn't support apng

https://tenor.com/view/cat-unicorn-rainbow-gif-12911499

https://c.tenor.com/QnDRbF8idrUAAAAM/spiderman-deadpool.gif

https://en.wikipedia.org/wiki/Rat

https://en.wikipedia.org/wiki/Continuous_uniform_distribution

https://en.m.wikipedia.org/wiki/Colors_of_noise

https://youtu.be/P_Oh7HizY5I

/dev/urandom

I wonder who came up with that HBO intro

> Type cat vmlinuz > /dev/audio to hear the Voice of God.

Great idea for video streaming, start every single thing you make with a good chunk of almost pure entropy

Or would they have found a way to encode that part using grain synthesis or other tricks?

In jxl there is pseudorandom noise generation, but even if it wasn't there, you could probably cheaply encode something that looks pretty random using MA trees that represent a suitable cellular automaton: https://cloudinary.com/blog/compressing_cellular_automata

HBO had that noise intro since at least 1983: https://www.youtube.com/watch?v=i1NKoMNy5bY I doubt there was much digital about it at the time.

Hmm, no looking at the rest, it probably was digital.

The best way to encode those is now jxl btw, no longer flif. Jxl can encode contexts with a singleton histogram with 0 bits instead of the fraction of a bit flif needs to do a bit with 4095/4096 chance

FFS geographical restrictions.

Why would they do that? It's not like they are paying for the bandwidth...

Very random password

zsh doesn't allow it and bash doesn't do anything<:SadCat:805389277247701002>

It's a quote I first read somewhere in the previous millennium. /dev/audio predates OSS even, which was later superseded by ALSA, and I have no clue what's used now.

> aplay /dev/random

to play your ram:

> sudo aplay /dev/mem

`aplay /boot/vmlinuz` also works.

Can probably also `convert` it into an image if you specify some dimensions and tell ImageMagick it's raw image data

although /dev/mem and /dev/kmem are often disabled to improve security

geez, I wonder why 😛

It's only a file that contains all the contents of your ram! What could go wrong? /s

https://tenor.com/view/templeos-terry-davis-gif-19184988

Jon on next JPEG meeting: - EMOJIS.. on my discord, new emojis so sick, we have eight new pepelaugh and three kekw - What about codec? - ..Yeah, it's good too.. working on stuff

I have been aware Discord doesn't support apng for some time

If JXL beats FLIF in theory for CA images, I wonder what is needed in practice, since currently it seems like no options to cjxl gets it anywhere close to FLIF (though much better than PNG ofc).

CA images?

cellular automata

Ah.

FLIF seems to be pretty good at learning the CA rule used, with pretty fast encode times too.

FLIF is not tiled, so in that respect it has an advantage in compression. Can set cjxl to do `-g 3` to make large tiles.

Probably also need `-s 9 -I 1` to have a chance at finding the CA rule

The tree learning algorithm in cjxl is not really tested on edge cases like CA images

But the jxl MA trees are more expressive than the flif ones, and also they effectively can be a DAG.

<@799692065771749416> instead of the adaptive range coder from ffv1 with the exp-mantissa representation with a lot of branching, we now use fixed histograms per context, encoded in a hybrid way as an ANS token for exponent plus configurable number of msb and lsb, with any remaining bits (if any) encoded raw. Plus an option to have a token to encode lz77 references.

That's significantly faster to decode because the branching of bit-by-bit range coding is avoided. It's also better to just encode histograms than to rely on adaptation (and more expressive than one chance per bit). The special case of a context where prediction is perfect (i.e. all values are zero) does occur, and those values can be compressed to zero bits instead of some small fraction of a bit.

There's also an option to use simple prefix coding instead of ANS. It is worse, but easier for the encoder.

Alright, the rule 1599 image from the article that flif does at 899 bytes is 1102 with `-s 9 -g 3 -I 1`, 1111 with `-s 9 -g 3`, 6330 with `-s 9 -I 1`, and 6379 with `-s 9`.

😱

Not unexpected, at the group boundaries jxl needs to do a row and a column of non-predicted pixels

<@794205442175402004> Can you elaborate (or link to a writeup) on what you mean with fixed histograms per context?

Per context, we signal a histogram for the tokens that are ANS encoded

Ah, the distribution is static, and encoded explicitly in the image file?

Yes, per context

You can still make it region-dependent, e.g. the x,y coordinates are things you can split on in a MA tree decision node

But presumably you don't actually encode a full distribution, just a few parameters?

Tokens can be e.g. like this: 0-15 represents values -7 to 8 directly 16-31 represents larger amplitude numbers, where 1 insignificant bit does not get entropy coded but just written raw separately 32-47 represents even larger amplitude, with 2 raw bits and so on

So in practice the max token value is often not that large

it's a full distribution with a few tricks to save bits in cases where they're not very much needed - also it's not one distribution per leaf but they are clustered

https://youtu.be/NnKhAkNestY

Feeling honored, main lead dev of PNG following me on twitter 😊

😄

I posted your codec summary text when Thomas was promoting WebP as a good replacement of PNG 🙂

It was impressive to people -- I got 10 more twitter followers as a result (+3 % followers)

the thing I like least in PNG is that in 16 bit PNGs the same entropy code is necessarily used for high and low byte

that reduces compression efficiency by 25 % or so

What is difference between this and offtopic?

Nobody knows

Ah

This was supposed to be an on-topic, but after some spam it became what it is

Nobody uniformly knows

If you spam a lot of flashing gifs it might get renamed to #epilepsy again :p <a:Hypercat:681237365599240216>

<:RaysCookie1:713195761508155463><:RaysCookie2:713195761348771862><:RaysCookie3:713195761361485876><:RaysCookie4:713195761575133245><:RaysCookie5:713195761453629492> <:RaysCookie6:713195761696768081><:RaysCookie7:713195762221056072><:RaysCookie8:713195761751293973><:RaysCookie9:713195762061672468><:RaysCookie10:713195761990631504> <:RaysCookie11:713195761688641627><:RaysCookie12:713195761860608041><:RaysCookie13:713195762074517594><:RaysCookie14:713195761915002942><:RaysCookie15:713195761994825748> <:RaysCookie16:713195761613144145><:RaysCookie17:713195761986306088><:RaysCookie18:713195761768202261><:RaysCookie19:713195761873190974><:RaysCookie20:713195761961271317> <:RaysCookie21:713195761973723237><:RaysCookie22:713195761990369300><:RaysCookie23:713195761482858528><:RaysCookie24:713195761873190972><:RaysCookie25:713195761743036456>

<:RaysZ1:687990181843959828><:RaysZ1:687990181843959828><:RaysZ3:687990181864669217><:RaysZ4:687990181688901638><:RaysZ1:687990181843959828> <:RaysZ6:687990181885771786><:RaysZ7:687990181911199774><:RaysZ8:687990183173685312><:RaysZ9:687990182695272458><:RaysZ10:687990182649004070> <:RaysZ11:687990182632620107><:RaysZ12:687990182577963052><:RaysZ13:687990182469042227><:RaysZ14:687990182347145258><:RaysZ15:687990182687014927> <:RaysZ16:687990182548340811><:RaysZ17:687990182330630184><:RaysZ18:687990182342950948><:RaysZ19:687990182644940810><:RaysZ20:687990182749667380> <:RaysZ21:687990182380961815><:RaysZ22:687990182468649016><:RaysZ23:687990182384762978><:RaysZ24:687990182649004060><:RaysZ25:687990182372442133>

This is somewhat more on topic than <#806898911091753051>

And also more random

Yes. It makes png effectively useless for 10-bit and 12-bit, which are the most common bit depths for HDR.

using the same entropy code for alpha (and red, green, blue) is also a lazy/weird decision

back in the day they used pixel graphics without antialiasing mostly, and palette with transparent pixels was good enough -- and for those modes png is ok

https://tenor.com/view/kitten-kittens-cute-pet-give-me-attention-gif-12816949

https://tenor.com/view/how-random-is-that-whats-happening-that-was-weird-whats-going-on-odd-gif-14192455

Lol Aldi

I approve of lekker sappige kleine appels.

Lol

I hate that word to be honest. "sappig" is just cursed

You hate juicy stuff with a passion, it seems

https://c.tenor.com/s9lwRBPo9OoAAAAM/jack-black-full-pull-fool2cool4school.gif

Channel doesn't work

<:kekw:758892021191934033>

No tools for you😆

There is no video, only subtitles

The video is in the subs?

This works too well

So well that 256x256 30 seconds weights 60 MB

183 MB uncompressed

It's a hack, and doesn't mkv use lz4 for subs, so it's commpression is going to be 💩

https://en.wikipedia.org/wiki/Poe's_law

Reminds me of that one Pop Team Epic subtitle torrent. One 13 min episode 42.9 GB in size. 1080p through .ass subtitles, compressed. Uncompressed version is 1.1 TB.

https://www.youtube.com/watch?v=4NS0RQxojKY

The absolute state of this discord))))

Benchmarking emojis

https://tenor.com/view/bongos-cat-dancing-vibe-edited-gif-19250605

off-topic > on-topic > epilepsy > uniformly-random > on-topic?

https://tenor.com/view/pedro-approves-pedrorc-pedroredcerberus-yes-agree-gif-11599348

https://tenor.com/view/malta-malta-gifs-travolta-xarabank-peppi-gif-18186341

When all the europeans and most of the north americans are asleep

Present!

(US west coast)

Good morning!

Meanwhile I'm still up in the middle of the night

I really need to get a better sleep schedule

I need to get the kids to school, and there's too much snow to do it in the usual way (cargo e-bike)

☃️

Nice, biking is great

Imagine having a good sleep schedule <a:eyesshaking:729661219547643945>

<:kekw:808717074305122316>

When you have school homework to do before the school starts.

That's what I did back in primary school.

Worst decisions ever.

I just figured out how to use gnu parallel

wow

my scripts run practically instantly

A little curious, what compressor similar SuperREP? original SuperREP is stop development, probably have a alternative compressor use huge dictionary on LZ77? SuperREP: huge-dictionary LZ77 preprocessor Description: SuperREP is the first LZ77 compressor that supports dictionaries larger than RAM available.

What does that do? Use disk instead of memory?

I don't really understand about SuperREP,

https://encode.su/threads/2839-REP-SREP-FreeArc-deduplication-engines Bulat Ziganshin Q: Can SREP process data from stdin to stdout? SREP deduplicates data on the distances larger than RAM available, which makes it impossible to use stdin+stdout on both compression and decompression stage. Something should be sacrificed and various SREP modes allows you to choose the victim. -f (Future-LZ) mode is ideal for installations and other single-compression multi-decompression scenarios. It sacrifices stdin on compression stage - input data are read twice. On the first pass we build a list of matches, the second pass inserts matches at the point of source data. On decompression, match data are saved at the source pos into RAM/vmfile and flushed at the destination pos. So, decompression requires to use as much RAM+vmfile as much match data may be need to stored at any point of file. default (index-LZ) mode is ideal for standalone SREP usage as well as quick compression. It sacrifices stdin on decompression stage - input data are read out-of-order. It saves index (list of matches) at the end of compressed file, so decompressor first reads the index, then returns to the start of file and performs exactly as Future-LZ decompressor. -o (IO-LZ) mode is just old mode from pre-3.0 versions. It sacrifices stdout on decompression. Matches are stored at their destination point, and on decompression their data are literally read from the decompressed file. Decompression doesn't allocate RAM itself, but seriously trash the disk cache, making it inferior to index-LZ mode.

Continuing the topic of lossless, game screenshots are very often saved and distributed on the Web in lossless format (including various galleries and discord channels), as well as copy-paste images or printscreanning in discord (and other similar services) saved to PNG by default. So if taking the total percentage of Internet images, it is a small number, but if considered certain sites and services, there lossless formats is the main use. Game screenshots are also an interesting kind of content, on the one hand it's artificial, including pixel art and 3D, but it can also be very similar to real photos. Btw https://framedsc.github.io/HallOfFramed/

And Digital Dreams Discord: <https://discord.gg/R3EKnTM>

Also on twitter you often see screenshots of tweets instead of quote tweets, for various reasons (so it survives deletion of the original tweet, people blocked by the tweet author can still see it, etc)

Yep, I wanted to collect screenshots with the text of tweets, discord and such for tests, but there are often abusive language there (also I wanted different languages, but I can't understand/translate everything) and also maybe they can't be re-published

Also the speed of the Internet in the world is growing, as well as decreasing the cost of storage, but the resolution of web images is not increasing so fast (especially images have long been much larger than the size of displays, unlike video), so the popularity of lossless will grow, even though lossy can be almost visually lossless (but still there are different criteria of quality for different people, for someone it is enough, for someone not, lossless has one - exactly as the original)

<@!503386653063118868>

yes daddy uwu