3 ms·
on the iPhone you can enable raw image output. No need for an external app. Just open settings.
by eek2121 3y ago
on the iPhone you can enable raw image output. No need for an external app. Just open settings.
- kalleboo 3y agoProRAW in the system app is still heavily processed, it just saves more of the intermediate data to let you tweak more of the processing stages. You still need a third party camera app to capture true RAW photos. E.g. with ProRAW you can't remove most of the noise reduction, and you can't rescue images with large white balance issues (you get fringing in one of the processing steps since the white balance is baked into several of the intermediate images)
- londons_explore 3y agoA 48 Mpixel 12 bit sensor with 128 frame stacking is 9 gigabytes of collected data per image. The flash memory isn't fast enough to store all of that in the ~2 seconds it is collected, nor is the RAM large enough to store it all. The iPhone is literally incapable of taking true RAW photos (at least not if you want to collect all the same info that the built in camera does)
- orbital-decay 3y agoNot sure I follow your logic, how did you end up with 9GB for a single shot, and why exactly 128 frames in 2 seconds? iPhone's hardware is more than adequate to capture RAW videos at 60fps with binning, not just photos (too bad Apple doesn't allow it, so it can't). People are using Android smartphones to shoot videos in RAW for several years already. OnePlus 8 Pro and later can easily capture a RAW stream in 4K 60fps.
- londons_explore 3y agoWhen you take a photo on iPhone, the image is composed of up to 128 frames taken before and after you hit the shutter button. Those frames are aligned and stacked using dedicated image processing silicon which can do that stuff reasonably power efficiently while working at those data rates. The stacking also allows things in the frame to move - it uses optical flow to track movement. That's how iPhone manages to take a tiny very noisy sensor and give non-noisy output. If you want to see how the camera performs without this stacking, try taking a photo from a moving car of something behind railings. The moving railings screw up the optical flow, so most of the 127 other frames will be discarded (if regions of an image arent a close enough match, then the region will be discarded), and you'll get to see all the sensor noise.
- orbital-decay 3y agoSure I know, GCam pioneered this years ago. But all those frames are merged into one which is written as a correct scene-referred DNG with the usual dimensions and the CFA pattern, as if it was taken by the sensor directly. Which is what GCam and every other app do. They don't write gigabytes of RAWs for a single shot. (although some apps do have that option, within the hardware capabilities) And all this has nothing to do with manual astrophotography, where you ditch computational apps, use a mount and shoot actual unstacked raw sensor frames with several seconds exposure each, interleaving them with dark frames, and do the computation yourself with the dedicated astrophoto software which is far better than any app if you calibrate the sequence and do the math correctly. Every phone is capable of this.
- kalleboo 3y agoYeah the RAW photos from third party apps are just a single frame, that's the point. It's the same thing as a RAW photo you'd get out of a standard digital camera.