That’s good news. I’ve watched a really good video in the last weeks about JPEG XL advantages, if you want to learn a bit more: https://youtube.com/watch?v=FlWjf8asI4Y
This may be a naive question but can't we have the features of JPEG XL combined with the compression algorithm of AVIF? Why does it have to be one or the other? Size clearly matters, especially for the majority of the world's population who do not have access to super fast internet and TBs of storage. It's definitely a luxury not having to care about file sizes.
To increase adoption they should not have limited this to the latest iPhone models. Why on earth can a one year old iPhone 15’s CPU not handle encoding JXL? It can encode 4K video in real time, so this should be no problem at all, right?
This is how they sell new phones. The grand majority of new features don't require the latest hardware, but artificially restricting it increases sales of new phones. None technical people can't usually tell the difference between hardware and software clearly enough to understand this nasty trick.
As Apple explains on the new iPhone models, JPEG XL files are supported
on iOS 17 and later and macOS 14 and later.
JPEG XL isn't limited to the latest phones; just a phone that can run iOS 17 or later. I have used JPEG XL on my iPhone 13 mini with no issues. iOS 17 runs on the iPhone XS (2018) or newer.
The difference is JPEG XL is now part of the Apple's image pipeline for the camera in iPhone 16.
Any 3rd party photo app developer can support JPEG XL if they wish.
One of the tricks for achieving the target battery life is that photo and video formats are offloaded to dedicated and very power-efficient hardware in all mobile devices. The iPhone 16 is the first to get hardware offload for AV1 and JXL, which is why it'll support these formats.
It's not just software, unlike in the PC world where going from 5W hardware decode to 50W software decode basically doesn't matter.
Reading the whole piece a few days ago, it's a pretty good overview of the promises of JPEG XL.
Apart from that, Apple's POV and PR bits being given such a central role felt a bit weird, especially as petapixel already spotted Samsung adopting JPEG XL months before Apple.
Aside from the petty "who was first" bickering, it's a completely different move to adopt a common standard already accepted by rival companies on the android side, and it means we can really expect a larger adoption of JPEG XL than the other standards Apple just pitched on its own.
That was the biggest beacon of hope IMHO, it would have benefited from more prominence.
Attaching any significance to being “first” on open standards is a game Apple rarely plays, but which others impose upon them because Apple’s adoption is (rightly or wrongly) seen as the most consequential and/or most newsworthy inflection point.
In terms of JPEG XL Lossless, Camera makers are already or has plan to adopt the format as RAW. In that space I think the adoption roadmap is quite good.
Thank god they went with a standard this time. When they launched HEIC, there wasn’t a single workable open source decoder. Hell, there wasn’t even a single non-Apple decoder.
An annoying oversight is that while my Fujifilm camera is modern enough to shoot HEIF+RAW, Apple Photos only knows to group JPEG+RAW as a single photo. Because Apple did not spend a day of engineering time bringing feature parity for the file format they themselves promoted, it has turned into a bigger feature to match and merge the HEIF and RAW assets after the fact. After several years, I'm growing doubtful they'll ever accomplish it.
I have yet to see whether they did it right with JXL+RAW (or is it DNG+RAW?) but hopefully they will before it becomes available in mainstream cameras.
> these .jxl files are wrapped in a DNG container, so you can’t just fire off .jxl files from the iPhone 16 Pro.
Any move toward JPEG XL support is good, but this is lame. Even if the Chrome team comes to its senses and restores jxl support you won't be able to view these files.
JPEG XL is a great name from a marketing perspective. The Apple roadmap has several successor compressors with AI elements in the planning sheet - JPEG XL PLUS, JPEG XL MAX. These formats will have small nominal yearly licensing fees to use. Finally, the most advanced format will be JPEG XXXL which they are developing in collaboration with pornhub.
Although it might seem confusing at first glance, having your selling point as "our file sizes are larger!" is so counterintuitive, that I think it's obviously not that!
The XL probably relates to the fact that the relative savings increase with higher res pictures. Whereas original jpeg's file size might have scaled linearly, jxl could do better than that.
JPEG XL also supports re-encoding existing JPEG files to decrease file size while keeping the original file quality. That really seems like useful feature but so far I haven’t seen any tooling (in macOS) to re-encode my existing photo library.
I don’t have iphone 16, and this article puzzles me.
Is apple only using jxl for their “raw” camera capture, but not regular camera capture?? The non-raw use case seems to be the one that would have more impact to regular folks.
Isn’t Samsung generally ahead of apple on most technical fronts though? Especially on mobile, I think people usually just assume apple just spends more effort on refining it, which is not a bad rule of thumb, but certainly not always the truth.
Yes, yes, but 48mP only, when will they finally have 240MP on a sensor that can be mounted on the ass of an ant. But double the protrusion 6 times I guess for the lens supporting the new tech and whatnot (tele-macro at night in a panoramic sport event!), it may even take picture for you without thinking taking a picture, you purchased a smartphone didn't you, let it be smart then, it will know better than you what you need, how you need it, and when you need it, all is necessary to fix it to your forehead so it can see what you see, tiny bitsy inconvenience beyond storing and managing the billboard sized but polaroid quality stream of pics vomited out by the device - never to see the most.
This good photo = phone deception marketers pushed on idiotic customers who actually pay the premium for the marketing material is pathetic.
[+] [-] nesk_|1 year ago|reply
[+] [-] hajhatten|1 year ago|reply
[+] [-] trompetenaccoun|1 year ago|reply
[+] [-] b15h0p|1 year ago|reply
[+] [-] WhyNotHugo|1 year ago|reply
[+] [-] alwillis|1 year ago|reply
The difference is JPEG XL is now part of the Apple's image pipeline for the camera in iPhone 16.
Any 3rd party photo app developer can support JPEG XL if they wish.
[+] [-] jiggawatts|1 year ago|reply
It's not just software, unlike in the PC world where going from 5W hardware decode to 50W software decode basically doesn't matter.
[+] [-] account42|1 year ago|reply
[+] [-] NinoScript|1 year ago|reply
[+] [-] cchi_co|1 year ago|reply
[+] [-] the4anoni|1 year ago|reply
[+] [-] FollowingTheDao|1 year ago|reply
[+] [-] brigade|1 year ago|reply
[+] [-] makeitdouble|1 year ago|reply
Apart from that, Apple's POV and PR bits being given such a central role felt a bit weird, especially as petapixel already spotted Samsung adopting JPEG XL months before Apple.
Aside from the petty "who was first" bickering, it's a completely different move to adopt a common standard already accepted by rival companies on the android side, and it means we can really expect a larger adoption of JPEG XL than the other standards Apple just pitched on its own.
That was the biggest beacon of hope IMHO, it would have benefited from more prominence.
[+] [-] simondotau|1 year ago|reply
[+] [-] alwillis|1 year ago|reply
JPEG XL was added to iOS 17 and macOS 14 last year [1].
[1]: https://developer.apple.com/wwdc23/10122
[+] [-] ksec|1 year ago|reply
[+] [-] scosman|1 year ago|reply
XL color depth looks amazing.
[+] [-] rgovostes|1 year ago|reply
I have yet to see whether they did it right with JXL+RAW (or is it DNG+RAW?) but hopefully they will before it becomes available in mainstream cameras.
[+] [-] happyopossum|1 year ago|reply
[+] [-] masklinn|1 year ago|reply
What?
[+] [-] modeless|1 year ago|reply
Any move toward JPEG XL support is good, but this is lame. Even if the Chrome team comes to its senses and restores jxl support you won't be able to view these files.
[+] [-] sho|1 year ago|reply
[+] [-] thecosmicfrog|1 year ago|reply
I still find JPEG "XL" to be such a bizarre name. I would intuitively think it would result in larger file sizes.
[+] [-] amy-petrik-214|1 year ago|reply
[+] [-] oneeyedpigeon|1 year ago|reply
[+] [-] bmicraft|1 year ago|reply
[+] [-] 1000100_1000101|1 year ago|reply
[+] [-] illiac786|1 year ago|reply
[+] [-] praseodym|1 year ago|reply
[+] [-] cherioo|1 year ago|reply
Is apple only using jxl for their “raw” camera capture, but not regular camera capture?? The non-raw use case seems to be the one that would have more impact to regular folks.
Why? Is jxl inferior to HEIC?
[+] [-] larrysalibra|1 year ago|reply
[+] [-] dsego|1 year ago|reply
I would've loved an explanation with this statement.
[+] [-] TiredOfLife|1 year ago|reply
note: the format was co-developed by Google who also makes Chome.
[+] [-] lonjil|1 year ago|reply
[+] [-] swiftcoder|1 year ago|reply
[+] [-] astrange|1 year ago|reply
[+] [-] EasyMark|1 year ago|reply
[+] [-] 7e|1 year ago|reply
[+] [-] weiliddat|1 year ago|reply
[+] [-] 0x69420|1 year ago|reply
[+] [-] lencastre|1 year ago|reply
[+] [-] unknown|1 year ago|reply
[deleted]
[+] [-] mihaaly|1 year ago|reply
This good photo = phone deception marketers pushed on idiotic customers who actually pay the premium for the marketing material is pathetic.