@gianni@disobey.net
@gianni@disobey.net avatar

gianni

@gianni@disobey.net

Really into codecs. Immutable filesystem fan, JXL evangelist. CEO of The Radix Project. Studying at WPI. I'm searchable.

#opensource #linux #foss

This profile is from a federated server and may be incomplete. Browse more on the original instance.

gianni, to photography
@gianni@disobey.net avatar
gianni,
@gianni@disobey.net avatar
gianni, to internet
@gianni@disobey.net avatar

I'm on the wait list. My plan is to set it up with a link to my Mastodon account and nothing else; after that I will not be touching it again.

gianni, to random
@gianni@disobey.net avatar

"During our security research we found that smart phones with Qualcomm chip secretly send personal data to Qualcomm. This data is sent without user consent, unencrypted, and even when using a Google-free Android distribution."

Source: https://www.nitrokey.com/news/2023/smartphones-popular-qualcomm-chip-secretly-share-private-information-us-chip-maker

gianni, to random
@gianni@disobey.net avatar

@LinuxClaude Yeah, DDG is Bing without the data collection. Startpage just hasn't been snappy enough for me.

gianni, to random
@gianni@disobey.net avatar

@wb @RL_Dane Does JXL not have any directional prediction or shared data between blocks? How does it handle generation loss so well?

I assumed the VarDCT built on every coding technique that previous DCT variants used, although I’m not well versed in what those were & I may be off base

gianni,
@gianni@disobey.net avatar

@wb @RL_Dane That's really interesting! Also seems like an easy way to hold video-based image formats back, if there are places where they won't ever improve because of the fact that everything needs to be hardware compatible (which iirc, hardware decoding isn't done for video-baned image codecs)

gianni,
@gianni@disobey.net avatar

@RL_Dane
I think smartphone ISPs utilize hardware encoding right now for JPEG - not entirely sure though. They definitely do for HEIC if you're on an iPhone.

The early dawn of JPEG hardware was admittedly before my time, but hearing what you're saying, that sounds super interesting. I was born into a world where 'jpeg' and 'image' were basically already synonymous
@wb

gianni,
@gianni@disobey.net avatar

@RL_Dane
That sounds like an incredible experience. Looking back, it looks like DCT-based coding algorithms are what truly revolutionized lossy multimedia compression, and the way it happened was really interesting! Obviously I wasn't there so I can't say much, but that's really cool
@wb

gianni,
@gianni@disobey.net avatar

@RL_Dane
It's an h265 I-frame, and I believe video encoding hardware is used. I don't own an iPhone so I haven't looked into it too much.
@wb

gianni,
@gianni@disobey.net avatar

@wb
I've only ever heard about JPEG's origins. Experiencing them - and helping cultivate them - must have been a uniquely incredible experience. I can only imagine seeing an innovation that I was a part of completely change the world like JPEG did.
@RL_Dane

gianni,
@gianni@disobey.net avatar

@RL_Dane
Precisely. Only implementing a subset of a codec's possible features to help lower costs & increase speeds is a no-brainer for a hardware encoder, especially when speed is usually the most important factor. You're right about high bitrate too, fancy lossy coding techniques for smaller filesize aren't as important when filesize is secondary to speed & fidelity
@wb

gianni,
@gianni@disobey.net avatar

@RL_Dane
Because smartphone photos look like trash (being a bit cheeky here) most of the time, I usually resize them and then convert. ImageMagick does work with JXL if compiled to work with it, like the imagemagick-full package in the AUR. I usually compress smartphone pics to AVIF because I am usually targeting medium/low-medium fidelity
@wb

gianni,
@gianni@disobey.net avatar

@wb
I think for video, hardware AV1 encoding couldn't make more sense. My guess is that's what RL_Dane is referring to with "high bitrates" - I would assume hardware AVIF would probably not be a very worthy endeavor, unless you need higher bit depth or HDR
@RL_Dane

gianni,
@gianni@disobey.net avatar

@wb
Considering smartphone photos are generally smoothed out oversharpened crap, I'm willing to write the entire sector's decisions off as nonsensical when it comes to image encoding. At least in the Android world, JPEG still largely reigns supreme.
@RL_Dane

gianni,
@gianni@disobey.net avatar

@RL_Dane
Yeah, and that h265 video will probably look as good as h264 medium or fast, my guess.
@wb

gianni, to random
@gianni@disobey.net avatar

Nvidia & Intel both have hardware accelerated AV1 encoding. Would u like to know which encoder performs better, among other things? Take a look at my blog post here: https://giannirosato.com/blog/post/nvenc-v-qsv/

gianni, to internet
@gianni@disobey.net avatar
gianni, to internet
@gianni@disobey.net avatar

Thorium’s JXL patch is now BSD. This more permissive license will allow basically any Chromium-based browser to implement JPEG-XL support, as the hard work has been done for them.

https://github.com/Alex313031/thorium-libjxl/commit/aa6b1603c5efd7b371f607fd2be736dedb11a8a8

gianni, to chrome
@gianni@disobey.net avatar

My image codec benchmarking blog post is up! Please have a look if you're interested!

https://giannirosato.com/blog/post/image-comparison/

gianni, to random
@gianni@disobey.net avatar

New Year’s resolution: 10-bit everything

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • kavyap
  • DreamBathrooms
  • thenastyranch
  • magazineikmin
  • InstantRegret
  • GTA5RPClips
  • Youngstown
  • everett
  • slotface
  • rosin
  • osvaldo12
  • mdbf
  • ngwrru68w68
  • megavids
  • cubers
  • modclub
  • normalnudes
  • tester
  • khanakhh
  • Durango
  • ethstaker
  • tacticalgear
  • Leos
  • provamag3
  • anitta
  • cisconetworking
  • lostlight
  • All magazines