@jkoan@hammy@nate@radix Hi, we're still unfortunately dealing with registration. The IRS has requested more information twice now, and it usually takes around 4 months to get a response.
I must say, I really like the QOI image codec despite its shortcomings for coding efficiency and flexibility - it is dead simple, easy to implement, and super effective for what it is! I'd be happy in a world where we used QOI instead of PNG for a lot of stuff. And I've already fallen in love with Zig, which I think is very easy :)
The OnePlus Watch 2 is here, and it’s quickly become my favorite Wear OS smartwatch after only a few days of use! Its battery life has been STELLAR - it lasted me 75 hours during the first cycle! This is thanks to its huge battery (500mAh versus 306mAh in the Pixel Watch 2) and also Google’s new Wear OS hybrid OS interface.
I’ll share my full impressions on tomorrow’s episode of the Android Faithful podcast, but here’s a rundown of the key specs and features:
@MishaalRahman I have the first-gen OnePlus Watch, and it honestly kind of soured my impression of OnePlus's ability to make watches. Is this one a significantly better experience?
@MishaalRahman I'm aware, but I'm really interested in the specific experiential differences between the two. For example, the first gen watch got around 10-14 days of battery life in my experience during the first couple of months of use
The Tensor G3 is the first smartphone SoC to support hardware-accelerated AV1 encoding. It supports AV1 encoding at up to 4K60. No application (including the Pixel Camera app) takes advantage of this, though, likely due to a lack of platform support.
@MishaalRahman It is exposed via FFmpeg, but the resulting bitstream lacks any metadata regardless of the specified container format so the files are unplayable.
@MishaalRahman I definitely tried to try it out, haha. I was doing visual quality testing across all of the hardware encoders present in Tensor G3 when I came upon the Google AV1 encoding block which is distinct from the Exynos blocks. The fact that it doesn't write any container metadata makes it appear impossible to use, though; I haven't found a way around that.
"... Interop 2024 omits JPEG XL, the most popular proposal as measured by community reactions (emojis added to proposal discussion threads). JPEG XL garnered 646 reactions, more than four times more than the second place finisher, which also wasn't included."
An unfortunate conclusion from a clearly biased group that is supposed to be unbiased. Unfortunate, unclear decision making from Interop this year.
@Jain I say with near certainty there will be an AV2F, a VIC (VVC-derived image format), and maybe even a WebP v2 in the next 5 years. None will be nearly as promising as JPEG-XL is at this very moment. AVIF is a good image format, but has crippling limitations that JXL will simply never have and that AVIF successors will not desire to fix. The "best" image format isn't just the one with the best lossy compression.
@Jain I think you'd be very surprised to hear that AVIF is lacking features and aptitude in areas where codecs like JPEG & PNG aren't. I'll let you read more on the Codec Wiki: https://wiki.x266.mov/docs/images/AVIF
@Jain JXL isn't needless feature creep; that's what the video-based codecs are. You're thinking from a purely web-based standpoint here. JXL would be the only promising image codec to hopefully not need to look at another one for a very long time. I can tell you right now that professional photography, medical imaging, astrophotography, etc are simply not interested in AVIF, while JXL has the features to make everyone happy across the Web and beyond
@Jain Implementing too many codecs at once can get messy, which is why a new video-based codec every couple of years is an unfortunate sight to see, in my opinion. Especially considering WebP's failure (except the lossless part).
The AVIF spec was actually submitted as a proposal for JXL, but was rejected. That should have been the sign to relinquish AVIF development, if implementing things "together in a random order" is bad for the Web since it was known it would overlap with JXL which was always supposed to be a superset of AVIF or something better.
Regarding interest from professional use cases, I've seen JPEG XL discussed for these use cases in the JXL Discord. The JPEG XL project itself touts features like wide dynamic range support, layers, excellent lossless compression, and an incredible number of possible channels. Aside from HDR, the above are missing from AVIF. So, while adoption is still early, there is excitement about having a modern codec that can handle specialized needs beyond what JPEG and PNG currently offer. More info on JXL: https://wiki.x266.mov/docs/images/JXL
HEIC is not supported pretty much at all on the Web due to licensing restrictions, which make it very difficult to ship HEIC images. I would say AVIF has the most momentum now, even moreso than HEIC, but JPEG-XL and other future formats could gain traction once native browser support spreads.
Apparently the #samsung Galaxy S24's "downloadable" Gallery app (not sure what this means) supports JPEG-XL compression in RAW images!
> Downlodable App
> 1. Expert RAW
> The basic resolution has been improved from 12MP to 24MP, and image quality and tone in low light have been improved through nightography technology collaboration.
> In addition, Digital ND filter, which was supported as beta in previous S23, is officially provided and Auto mode is provided for user convenience.
> Additionally, storage capacity has been reduced while maintaining image quality by providing JPEG XL format.
Aviator is an app that lets your encode all your video files into the most modern open codec around, AV1! Change all of the provided encoding options if you so desire - set the image crop and the audio volume - or just appreciate the more efficient files you get from the process. From movies to gameplay clips, the sky's the limit with encoding in Aviator!