this post was submitted on 08 Aug 2025

466 points (98.9% liked)

Lemmy Shitpost

34167 readers

3682 users here now

Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.

Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!

Rules:

1. Be Respectful

Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.

Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.

...

2. No Illegal Content

Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.

That means:

-No promoting violence/threats against any individuals

-No CSA content or Revenge Porn

-No sharing private/personal information (Doxxing)

...

3. No Spam

Posting the same post, no matter the intent is against the rules.

-If you have posted content, please refrain from re-posting said content within this community.

-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.

-No posting Scams/Advertisements/Phishing Links/IP Grabbers

-No Bots, Bots will be banned from the community.

...

4. No Porn/Explicit

Content

-Do not post explicit content. Lemmy.World is not the instance for NSFW content.

-Do not post Gore or Shock Content.

...

5. No Enciting Harassment,

Brigading, Doxxing or Witch Hunts

-Do not Brigade other Communities

-No calls to action against other communities/users within Lemmy or outside of Lemmy.

-No Witch Hunts against users/communities.

-No content that harasses members within or outside of the community.

...

6. NSFW should be behind NSFW tags.

-Content that is NSFW should be behind NSFW tags.

-Content that might be distressing should be kept behind NSFW tags.

...

If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.

Also check out:

Partnered Communities:

1.Memes

2.Lemmy Review

3.Mildly Infuriating

4.Lemmy Be Wholesome

5.No Stupid Questions

10.LinuxMemes (Linux themed memes)

Reach out to

All communities included on the sidebar are to be made in compliance with the instance rules. Striker

founded 2 years ago

MODERATORS

STRIKINGdebate2@lemmy.world

LillianVS@lemmy.world

WiildFiire@lemmy.world

Decoy321@lemmy.world

Thekingoflorda@lemmy.world

YoBuckStopsHere@lemmy.world

The_Picard_Maneuver@startrek.website

FlyingSquid@lemmy.world

The_Picard_Maneuver@lemmy.world

466

My latest hyperfixation (lemmy.librebun.com)

submitted 3 weeks ago* (last edited 3 weeks ago) by sailorzoop@lemmy.librebun.com to c/lemmyshitpost@lemmy.world

61 comments fedilink hide all child comments

Somebody save my CPU. made with Krita™

top 50 comments

sorted by: hot top controversial new old

[–] ZkhqrD5o@lemmy.world 84 points 3 weeks ago* (last edited 2 weeks ago) (4 children)

I'll take any excuse I can get to dump my perspective here. I love AV1 for video and I hate AVIF with a passion. Every video that I create is delivered in AV1, because it is incredibly useful, versatile and extremely powerful. Right tool for the right job.

Not that there's anything inherently wrong with AVIF other than it tries to force a video codec into something that is that it is not meant for, namely a still image codec. I hate the drama around it that Google has created. Because the stupid cunt that created AVIF is an emotional slime, he tried to block JPGXL, a competitor for AVIF, from having official support in the Google Chrome browser. And because Google Chrome is a monopoly in the browser market, CDNs and other people who'd like to use JPGXL, since it has significantly better all around features for still images, cannot use it now.

Features of JPEG-XL:

better still image compression than AVIF
lossless JPEG transcoding
progressive image loading
universally usable from capture to delivery
layer support with 4,099 channels
CMYK Compatible
32 bits per channel
no limitations on image size or colour precision

And all of that is thrown away because one bastard has his feelings hurt by user choice.

Thank you for listening to my useless TED Talk.

Edit: While I sound extremely black-pilled about this, because monopolies are bad, the positive thing is that it's gaining traction, finally. Apple has fully embraced it some time ago. Now Microsoft Windows supports it natively as well. Literally the only missing piece is the browser. While Safari, thanks to Apple, - never thought I'd say that - now supports JPEG XL natively, Firefox and Google Chrome do not as of right now. So the browser is literally the last missing link for full native support. Also, I'd wish for the people at Mozilla to stop letting themselves be cucked by Google. But JPEG XL is around the corner, luckily, because sooner or later they will be forced to use the modern format to stay competitive, like Samsung already does for their phone cameras. Still salty about the attempt, though.

[–] sailorzoop@lemmy.librebun.com 22 points 3 weeks ago (1 children)

Thank you for your TED Talk. I had no idea about the creator of AVIF or anything, BUT, I still really like that I can just use the same knowledge when it comes to transcoding jpegs/whatever to it. It uses the same codec, same parameters, supports animations, is like 1/100th the size of gifs...
I guess webp can do that latter part as well, but having a single tool able to do these things is neat in my opinion. (Please don't come at me, systemd haters)
I think jxl also supports waaaaay higher resolutions and everything. So yeah, fair argument that I'm not, in any way, against.
Compression and accessibility are just really fascinating things to me, and I'm sure once the next huge, well-supported thing, comes around, so will I.

[–] ZkhqrD5o@lemmy.world 9 points 2 weeks ago

Yes, and I agree with you. People should have choice of what format they use because different people have different needs.

I don't hate AVIF inherently for its technology. I hate it for what it stands for. Namely, megacorporation Culture. One rogue manager has their feelings hurt and everyone bends over to accommodate them. Google has a fully SIMDified Rust decoder for JPEG XL that is fully standard compliant. But it doesn't go into Chrome, because everyone just parrots the one guy that once made up some lie about it not "having public interest". Best example is Google Interop 2025 not taking in JPEG XL. Literally every graphics software on the planet supports it, as well as multiple newspapers and CDNs want to use it, and I don't mean the newspaper next door, I mean newspapers like The Guardian and CDNs like cloudflare. You can call Apple a lot, but the jpeg-xl implementation is some objective good for computing, Microsoft is slowly but surely rolling out support in Windows as well. Literally the only missing link in the chain is the Google Chrome browser, because it's a monopoly.

And with that, I refuse to use it. Because if I were to use it and pump the numbers for AVIF, I would reinforce the blockade. Therefore I just can't, even though the technology is very useful and that's just another side of the Google Monopoly.

[–] daggermoon@lemmy.world 7 points 3 weeks ago

I converted most of my images to .jxl. It's been pretty nice.

[–] haerrii@feddit.org 5 points 3 weeks ago (1 children)

I wonder how we're feeling for HEIC? Any drama/pros/cons I should know of? As AAPLs weight is behind, I wonder if we'll get browser wars for this decades' image formats.

[–] blah3166@piefed.social 15 points 3 weeks ago (1 children)

HEIC faces a few struggles with adoption:

It's patent encumbered.
It's not free as in "free beer", someone has to pay for it.
It's not free as in "free speech" - you can't use, modify, and distribute software or formats without restrictions due issue #1.

AV1 and AVIF don't have any of these issues –someone correct me if I'm wrong or missing something– so anyone is able to include/distribute the software and modify to their needs.

[–] haerrii@feddit.org 2 points 2 weeks ago

Ahh I see. I'm curious what the future holds lol

[–] AdrianTheFrog@lemmy.world 2 points 2 weeks ago

ldk, avif looks really good at the really high compression ratios. My problem with it is that usually it includes lots of details, except those details weren't the actual details of the original image. It just kinda hallucinates them

Also ofc the unlimited layers, great lossless mode, and high color depth etc would still make jxl a better universal choice, but avif just looks better at the ultra low end

[–] circuitfarmer@lemmy.world 27 points 3 weeks ago (2 children)

Not only is everything smaller, but the codec looks better. Compression artifacts when AV1 is really pushing it at lower bitrates are more like... pointillism? They resemble grain instead of the fuzzy squares you can get with 264 or 265, and it is especially better in dark scenes.

[–] WolfLink@sh.itjust.works 18 points 3 weeks ago (3 children)

But it looks much worse at higher bitrates. H265 can get decent bitrates and have no visible difference from the original. AV1 loses a bunch of quality right out of the gate. If you are wanting to archive footage I think h265 is much better.

[–] circuitfarmer@lemmy.world 6 points 3 weeks ago (1 children)

I don't disagree about archiving. Though for a local collection, I think the space savings of AV1 are worth it.

Especially for grainy footage, which is extra costly in h265. The noise analysis and synthesis in AV1 is killer, IMHO. But of course... it's not the same noise.

load more comments (1 replies)

[–] ZkhqrD5o@lemmy.world 5 points 2 weeks ago

The newer iPhone models actually capture their images as JPEG XL and they have retired their HEIC images. All of Apple's software has full native support for JPEG XL as well.

[–] gnuplusmatt@reddthat.com 2 points 3 weeks ago (1 children)

are you archiving it until the patents expire? I use AV1 because of the license

[–] WolfLink@sh.itjust.works 3 points 3 weeks ago

I’m not really worried about the licensing of the codec I use for my personal archive. Even if I was worried, I would use h264 or VP9 before I used AV1.

load more comments (1 replies)

[–] db2@lemmy.world 12 points 3 weeks ago (2 children)

Disk is cheap, just make everything mpeg2.

[–] sailorzoop@lemmy.librebun.com 14 points 3 weeks ago

bring back .3gp to share with your classmates

[–] gens@programming.dev 7 points 3 weeks ago

Just download it in tiff 16bit

https://durian.blender.org/download/

15min movie 53GB zipped

[–] sailorzoop@lemmy.librebun.com 11 points 3 weeks ago* (last edited 3 weeks ago) (2 children)

Why didn't it fully embed the avif 😭
Edit 1: Might be just jerboa.. Yahaw it's investigation time.
Edit 2: Shows up fine on Lemmy-ui, Photon, Raccoon but not Jerboa and Thunder!

[–] ZkhqrD5o@lemmy.world 4 points 3 weeks ago

In Voyager, everything works.

[–] Armand1@lemmy.world 11 points 3 weeks ago* (last edited 3 weeks ago) (2 children)

I tried AV1, but it seems to work really poorly for compressing film grain which is my main usecase (movies).

I realise you can add fake film grain, but that's not really my thing.

I'm sure it's great for video game footage or low grain modern video, but that's not what I need it for.

For now, I'll likely stick with x265.

[–] Pyroglyph@lemmy.world 5 points 3 weeks ago (3 children)

I could be wrong, but isn't the idea that it removes the film grain to aid compressing the ""actual"" image behind the grain, and then the player adds the grain back in during playback?

The way you say it makes it sound like you want to compress the grain itself, and that sounds to me like a "I like the vinyl crackle in my digital media" take. Not that that's a bad thing, everyone has preferences, but it's also unlikely that AV1 (or any codec for that matter) was designed with the preservation of accurate film grain in mind.

load more comments (3 replies)

load more comments (1 replies)

[–] exu@feditown.com 11 points 3 weeks ago (5 children)

Ah, but are you using aomenc, SVT-AV1 or rav1e? Or one of the forks maybe?

[–] sailorzoop@lemmy.librebun.com 8 points 3 weeks ago (2 children)

I've tried all three! SVT flies in comparison to AOM on my 5800X.
Still playing around with ffmpeg settings, film grain synthesis and planning on properly checking out av1an.
I just love the codec so much, tiny bitrates but still beautiful. Then I learned .avif uses the same libraries as well and takes up like 1/10th of what my pngs do. (played around with webp/m before, pretty impressed with that as well..)
Wonderful stuff

[–] scholar@lemmy.world 7 points 3 weeks ago

If you have lots of jpgs you can losslessly reencode them to jpegxl and make them ~20-30% smaller (or absolutely shrink them with barely any noticable quality loss)

[–] ChaoticNeutralCzech@feddit.org 2 points 3 weeks ago* (last edited 2 weeks ago)

Same here, I wonder why SVT is not included with ffmpeg's standard compile flags. Licencing?

The era of decent full HD movies on CD has come, finally a use for all my CD-R spindles!

[–] brucethemoose@lemmy.world 3 points 2 weeks ago* (last edited 2 weeks ago)

av1an with its dark scene boost/per scene tuning is the best.

It works with x265 (or hardware encoders) too.

load more comments (3 replies)

[–] JohnWorks@sh.itjust.works 10 points 3 weeks ago

FINALLY MY KINDA WOMAN

[–] safesyrup@feddit.org 5 points 3 weeks ago (3 children)

GPU acceleration is your friend :D

[–] exu@feditown.com 10 points 3 weeks ago

Software encoders are better for archiving as they are more efficient with their bitrate. You either get better quality with the same size or a smaller file than hardware encoders.

[–] AnUnusualRelic@lemmy.world 2 points 3 weeks ago (1 children)

What if I offload it to my 487?

load more comments (1 replies)

[–] Electricd@lemmybefree.net 5 points 2 weeks ago

Let’s Jellyfin and chill

[–] Pudutr0n@feddit.cl 4 points 3 weeks ago

Shut up and -crf 0 me.

[–] Routhinator@startrek.website 4 points 2 weeks ago (2 children)

Tdarr.

[–] interdimensionalmeme@lemmy.ml 2 points 2 weeks ago

wow that's bad ass, can we game on that ? What about running private-ish AI ?

[–] Passerby6497@lemmy.world 2 points 2 weeks ago (1 children)

I think FileFlows is better. I used tdarr for a few years, but I couldn't get back into it after I had an m.2 burn itself out and I didn't have good backups. I tired to set it back up and didn't have enough patience to get it working again, and FileFlows was a drop in replacement that required minimal setup to get everything running again.

[–] Routhinator@startrek.website 2 points 2 weeks ago (1 children)

I haven't seen that one. Tdarr used to be more work to get going with classic plugins, but with Flows its really intuitive and I've codified my flows into the helm chart I deploy it with so I don't need to think about it. Its all in git and commented well.

[–] Routhinator@startrek.website 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Huh.. FileFlows does a lot more than video and music though... interesting.

Eh there are a couple of things I dislike, though the UI is very nice looking and there are lots of features. Closed source, no lifetime option and tiered subs... that all puts me off a tool pretty quickly these days. I've lost the ability to trust anything that does not have open code due to the never ending and constant corporate enshittification and underhanded tracking.

load more comments (1 replies)

[–] Magister@lemmy.world 4 points 3 weeks ago (1 children)

but... HEVC?

[–] sailorzoop@lemmy.librebun.com 7 points 3 weeks ago (1 children)

There are still a lot of issues with adaptation of HEVC, especially with chromium based browsers on linux. Probably due to the patent fees or... whatever.
https://forum.endeavouros.com/t/hevc-support-and-cpu-load-in-brave-or-vivaldi-browser/72984
https://github.com/brave/brave-browser/issues/40101
This isn't just a Brave issue, but affects basically all Chromium forks other than Thorium and... the other one I forgot the name of lol.
I can't play any of the example hevc encodes, regardless of used flags/arguments. Vaapi set up correctly, and working everywhere else.

BUT, for the one person on here with the same issue, using Jellyfin. Thorium browser gets updated once in a blue moon, but does have a workaround for HEVC decoding, and if you don't wanna use that, Jellyfin Media Player seems to be using mpv as the player backend, doesn't seem to be just an electron wrapper, and works great.
Furryfox works fine too.

[–] Magister@lemmy.world 4 points 3 weeks ago (1 children)

I'm using MX Linux and Firefox, I'll test the browser. But using VLC it's no problem here.

[–] sailorzoop@lemmy.librebun.com 2 points 3 weeks ago

Yeah, external players like mpv and vlc are perfectly fine. Works on FF for me too. Seems like the issue pops up every couple of months with droves of people posting on random forums all around.

[–] WolfLink@sh.itjust.works 3 points 3 weeks ago

I did a comparison of AV1 vs h265 on a handful of video files I have in different styles. H265 seemed consistently better. AV1 just crushes the quality way too much.

[–] jsomae@lemmy.ml 3 points 2 weeks ago

This is what I subscribe to lemmy for.

[–] brucethemoose@lemmy.world 3 points 2 weeks ago* (last edited 2 weeks ago)

Just wait until you discover vapoursynth.

[–] ConstantPain@lemmy.world 2 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

Clicked the link and was instantly blocked. WTF

[–] ConstantPain@lemmy.world 3 points 2 weeks ago (3 children)

load more comments (3 replies)

[–] sailorzoop@lemmy.librebun.com 2 points 2 weeks ago

What?... My power just went out, are you talking about the cloudflare 404? lol

[–] dajoho@sh.itjust.works 2 points 2 weeks ago

All VP9 and Opus here, but I have a similar fixation. Wouldn't find this lady odd at all.

load more comments