Remix clone Hacker News

The main reason is that image Quality is the main coefficient of their corporation. They felt that it was a competitive advantage, and sort of a "secret ingredient," like you will hear from master chefs.

They feel that their images have a "corporate fingerprint," and are always concerned that images not get out, that don't demonstrate that.

This often resulted in difficulty, getting sample images.

Also, for things like chromatic aberration correction, you could add metadata that describes the lens that took the picture, and use that to inform the correction algorithm.

In many cases, a lens that displays chromatic aberration is an embarrassment. It's one of those "dirty little secrets," that camera manufacturers don't want to admit exists.

As they started producing cheaper lenses, with less glass, they would get more ChrAb, and they didn't want people to see that.

Raw files are where you can compensate for that, with the least impact on image quality. You can have ChrAb correction, applied after the demosaic, but it will be "lossy." If you can apply it before, you can minimize data loss. Same with noise reduction.

Many folks here, would absolutely freak, if they saw the complexity of our deBayer filter. It was a pretty massive bit of code.

▲

Zak 11 days ago | parent | next [-]

Thanks for the explanation. I have to question how reality-based that thinking is. I do not, of course expect you to defend it.

It seems to me that nearly all photographers who are particularly concerned with image quality shoot raw and use third-party processing software. Perhaps that's a decision not rooted firmly in reality, but it would take a massive effort focused on software UX to get very many to switch to first-party software.

> Raw files are where you can compensate for that, with the least impact on image quality. You can have ChrAb correction, applied after the demosaic, but it will be "lossy."

Are you saying that they're baking chromatic aberration corrections into the raw files themselves so that third-party software can't detect it? I know the trend lately is to tolerate more software-correctable flaws in lenses today because it allows for gains elsewhere (often sharpness or size, not just price), but I'm used to seeing those corrections as a step in the raw development pipeline which software can toggle.

▲

ChrisMarshallNY 11 days ago | parent [-]

I think we're getting into that stuff that I don't want to elaborate on. They would probably get cranky I have said what I've said, but that's pretty common knowledge.

If the third-party stuff has access to the raw Bayer format, they can do pretty much anything. They may not have the actual manufacturer data on lenses, but they may be able to do a lot.

Also, 50MP, lossless-compressed (or uncompressed) 16-bit-per-channel images tend to be big. It takes a lot to process them; especially if you have time constraints (like video). Remember that these devices have their own, low-power processors, and they need to handle the data. If we wrote host software to provide matching processing, we needed to mimic what the device firmware did. You don't necessarily have that issue, with third-party pipelines, as no one expects them to match.

	▲	Zak 11 days ago \| parent [-]
		Thanks for sharing what you could. I wasn't really thinking about video; the storage requirements to work with raw video are indeed big.

▲

porphyra 11 days ago | parent | prev [-]

I am very skeptical that chromatic aberration can be applied before a demosaic and then the result can be stored in a Bayer array again. There seems to be no advantage in storing the result of chromatic aberration correction in a raw Bayer array, which has less information, than a full array with the three RGB values per pixel. Perhaps I am not understanding it correctly?

	▲	ChrisMarshallNY 11 days ago \| parent [-]
		It's not stored. It's applied to the raw Bayer data, every time, before demosaicing. Same with noise reduction. What you can store, is metadata that informs these "first step" filters, like lens data, and maybe other sensor readings. One of the advantages to proprietary data storage, is that you can have company-proprietary filters, that produce a "signature" effect. Third-party filters may get close to it (and may actually get "better" results), but it won't be the same, and won't look like what you see in the viewfinder.