Somebody save my CPU. made with Krita™

top 50 comments

sorted by: hot top controversial new old
[–] 86 points 1 year ago* (last edited 1 year ago) (7 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.

  • source
  • hideshow 7 child comments
  • [–] [S] 23 points 1 year ago (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 9 points 1 year 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.

  • source
  • parent
  • [–] 5 points 1 year ago (2 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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 16 points 1 year ago (1 child)

    HEIC faces a few struggles with adoption:

    1. It's patent encumbered.
    2. It's not free as in "free beer", someone has to pay for it.
    3. 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.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (1 reply)
    [+] 28 points 1 year ago* (last edited 5 months ago) (7 children)
  • [–] 17 points 1 year ago (5 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.

  • source
  • parent
  • hideshow 5 child comments
  • load more comments (1 reply)
    [–] 13 points 1 year ago (7 children)

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

  • source
  • hideshow 7 child comments
  • [–] [S] 9 points 1 year 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

  • source
  • parent
  • hideshow 2 child comments
  • load more comments (3 replies)
    [–] 13 points 1 year ago (2 children)

    Disk is cheap, just make everything mpeg2.

  • source
  • hideshow 2 child comments
  • [–] [S] 12 points 1 year 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!

  • source
  • hideshow 2 child comments
  • [–] 12 points 1 year ago* (5 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.

  • source
  • hideshow 5 child comments
  • [–] 5 points 1 year 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.

  • source
  • parent
  • hideshow 3 child comments
  • load more comments (3 replies)
  • I'm no expert on the grain side, but Netflix had a nice writeup about its power.

    https://netflixtechblog.com/av1-scale-film-grain-synthesis-the-awakening-ee09cfdff40b

    I also heard that when you use film grain, you should disable the denoising done on the output to properly preserve detail in the encoding. Which depends on the encoder, but should generally be possible on the ones that do film grain.

    But it might not be as good for artistic film grain that doesn't fit normal "grain" in videos.

  • source
  • parent
  • [–] 11 points 1 year ago

    FINALLY MY KINDA WOMAN

  • source
  • [–] 6 points 1 year ago

    Shut up and -crf 0 me.

  • source
  • [–] 5 points 1 year ago (4 children)

    GPU acceleration is your friend :D

  • source
  • hideshow 4 child comments
  • [–] 11 points 1 year 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.

  • source
  • parent
  • load more comments (1 reply)
    [–] 5 points 1 year ago

    Let’s Jellyfin and chill

  • source
  • [–] 4 points 1 year ago (5 children)
  • [–] 2 points 1 year ago (3 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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 1 year ago (2 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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago* (last edited 1 year ago) (1 child)

    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.

  • source
  • parent
  • hideshow 1 child comment
  • load more comments (1 reply)
  • [–] 4 points 1 year ago (3 children)
  • [–] [S] 8 points 1 year ago (2 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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 1 year ago (1 child)

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

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 1 year 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.

  • source
  • [–] 3 points 1 year ago*

    Just wait until you discover vapoursynth.

  • source
  • [–] 3 points 1 year ago

    This is what I subscribe to lemmy for.

  • source
  • [+] 2 points 1 year ago* (last edited 4 months ago)
    [–] 2 points 1 year ago* (5 children)

    Clicked the link and was instantly blocked. WTF

  • source
  • hideshow 5 child comments
  • load more comments
    view more: next ›