The Limits of Computational Photography

Re:The Limits of Computational Photography by kblev on Tuesday January 31, 2023 @06:33AM (#34593863)

Is there a way to disable this extra processing?

[ Parent | on HN ]

Re:The Limits of Computational Photography by npteljes on Tuesday January 31, 2023 @06:38AM (#34593893)

You can go around some of the extra processing by using other camera apps, for example "Open Camera". It can even shoot RAW photos, so that the least amount of processing is applied to the image. Unfortunately, you can't disable all of the processing, because some of it happen on the hardware, or in the camera's kernel module.

https://opencamera.org.uk/

[ Parent | on HN ]

Re:The Limits of Computational Photography by hapticmonkey on Tuesday January 31, 2023 @07:39AM (#34594343)

Shoot in RAW mode. Either with the various third party camera apps, or Apple’s built in “Pro RAW” mode in the iOS camera app.

[ Parent | on HN ]

Re:The Limits of Computational Photography by astrange on Tuesday January 31, 2023 @08:28AM (#34594745)

Third party camera apps don't use the Camera app processing whether or not they're shooting raw mode. You can shoot JPEGs all day.

[ Parent | on HN ]

Re:The Limits of Computational Photography by wyager on Tuesday January 31, 2023 @09:15AM (#34595233)

Sort of - (I assume for PR/marketing reasons) Apple doesn't let apps get access to actual raw sensor data. It may be possible to skip the steps that are causing the most trouble here.

[ Parent | on HN ]

Re:The Limits of Computational Photography by foldr on Tuesday January 31, 2023 @09:29AM (#34595391)

Why don't you just try shooting it ProRAW, then try shooting a single shot RAW using a third-party app such as Halide? The latter option certainly removes any fancy computational photography from the pipeline.

[ Parent | on HN ]