Marco Arment

It's the most noticeable, or excuse me, it is most noticeable on smooth gradients such as skies, but also architecture. Even P3 hits the upper bounds of eight bits. With today's tech, there really is no point shooting in limited JPEG. Modern Sonys can even shoot 10-bit HEK. But RAW is always preferred for portability.

It's the most noticeable, or excuse me, it is most noticeable on smooth gradients such as skies, but also architecture. Even P3 hits the upper bounds of eight bits. With today's tech, there really is no point shooting in limited JPEG. Modern Sonys can even shoot 10-bit HEK. But RAW is always preferred for portability.

All right. And then Leo continues, for HDR, always shoot raw. Lightroom takes all the bits of information. When you enable the HDR toggle, applies an appropriate tone curve automagically. Suddenly, everything that seemed overexposed shows details. For exporting, always use 16-bit JPEG XL or 10-bit AVIF. Then Josh Harris writes, thanks for the great discussion on editing photos.

All right. And then Leo continues, for HDR, always shoot raw. Lightroom takes all the bits of information. When you enable the HDR toggle, applies an appropriate tone curve automagically. Suddenly, everything that seemed overexposed shows details. For exporting, always use 16-bit JPEG XL or 10-bit AVIF. Then Josh Harris writes, thanks for the great discussion on editing photos.

What should I do with display settings like true tone, night shift, and brightness while editing? I always try to turn color shifting off and increase brightness, but I'm not sure what the best setting is for the most true-to-life result or whether the system adjusts for this already. I mean, I guess turn it all off if you can, but what a pain.

What should I do with display settings like true tone, night shift, and brightness while editing? I always try to turn color shifting off and increase brightness, but I'm not sure what the best setting is for the most true-to-life result or whether the system adjusts for this already. I mean, I guess turn it all off if you can, but what a pain.

Indeed. John, do you want to talk about cropping, please?

Indeed. John, do you want to talk about cropping, please?

With regard to parallelization for file compression and decompression, Mihai Paparita writes, the compression speed and parallelism discussion of the most recent ATP reminded me of Cigar JAWS XIP, unzip utility. Though it only focuses on decompression, it shows how much faster than archive utility you can be.

With regard to parallelization for file compression and decompression, Mihai Paparita writes, the compression speed and parallelism discussion of the most recent ATP reminded me of Cigar JAWS XIP, unzip utility. Though it only focuses on decompression, it shows how much faster than archive utility you can be.

This is relevant because Xcode is zipped using this, I guess, like secure XIP zip thing, and it takes four freaking ever to unzip it by default. Hmm. And so this is a open source and third party utility to make that faster.

This is relevant because Xcode is zipped using this, I guess, like secure XIP zip thing, and it takes four freaking ever to unzip it by default. Hmm. And so this is a open source and third party utility to make that faster.

Indeed. And then Cigar Jaw wrote in, or well, wrote on a thread that we were a part of and said, if you just use Finder to make a ZIP zip, it uses some single threaded code by default. I don't actually remember if you can make a zip in parallel, but I'm pretty sure even if you can, lib archive, whatever Finder uses, doesn't do that.

Indeed. And then Cigar Jaw wrote in, or well, wrote on a thread that we were a part of and said, if you just use Finder to make a ZIP zip, it uses some single threaded code by default. I don't actually remember if you can make a zip in parallel, but I'm pretty sure even if you can, lib archive, whatever Finder uses, doesn't do that.

However, Apple has a proprietary format that essentially makes a big tar of your files and then splits it into chunks to compress those in parallel. If your use case is, I have a chunkier file, please make it small, and you're okay with using a special Apple format, and also probably giving up a few percent in size, you should give it a try.

However, Apple has a proprietary format that essentially makes a big tar of your files and then splits it into chunks to compress those in parallel. If your use case is, I have a chunkier file, please make it small, and you're okay with using a special Apple format, and also probably giving up a few percent in size, you should give it a try.

If you're a developer, there's an API, which is the Apple Archive API. There's also an AA tool bundled with macOS that can create and manipulate Apple Archive files.

If you're a developer, there's an API, which is the Apple Archive API. There's also an AA tool bundled with macOS that can create and manipulate Apple Archive files.

All right. Dan Pierce wrote in with regard to the phones in schools overtime discussion from episode 607. Dan writes, my school had two main rules. This photo was in my yearbook. And you see, I guess, the staff of the high school. And this looks like in the gymnasium. They're on bleachers. And in the back, in huge letters, it reads as follows. No hats. No Walkman.

All right. Dan Pierce wrote in with regard to the phones in schools overtime discussion from episode 607. Dan writes, my school had two main rules. This photo was in my yearbook. And you see, I guess, the staff of the high school. And this looks like in the gymnasium. They're on bleachers. And in the back, in huge letters, it reads as follows. No hats. No Walkman.