848
Antworten
I'm comparing the file size: Just made a picture from my desk: Indigo DNG = 11,3MB, iPhone app (and ProCamera app) 27,1 MB: all with 26mm 12 MP
By @mopperle
My guess would be that native camera and ProCamera app are probably ProRaw with full RGB data, while Indigo is bayer raw data (only one color channel per pixel).
Thank you very much for the new recent update.
Everything stable on 16 Pro 🙏
It's good that they improved the Performance and make the app more stable. But please please add Different Aspect Ratios in the next Version. 16:9 and 2:1 would be very nice. I really wish I can shoot photos in horizontal mode for presenting on laptop or TV 🙂
By @Gehlich_Patrick4796
We are working on aspect ratio support. Please stay tuned.
Hello - testing the newest release and have selected DNG (only). When I tap on the image I see 'Preview only, tap here to develop the DNG.' That generates a .jpg and will continute to create additional .jpgs. Is this by design? Once it is processed and a .jpg is created why does it auto-generate another file?
By @cmgap
We decided to not do book-keeping in the background for such things and let the user control the file output. As Indigo progresses, we will update the processing so you may want to regenerate the JPEG from the DNG to compare, for example. Note that Indigo is experimental and our focus, as a small team, will primarily be on the image capture and processing algorithms - we fully appreciate that UX is a very important part of the app, but it is also one which can take a lot of resources away from the core problems we are trying to solve. In a case like this one, this was a conscious trade-off made by the team, and is something that should not be too difficult for the end user to learn and adapt to.
I recently used Indigo heavily for a trip and was just reviewing the photos. My impression of HDR is that sometimes it adds so much to the sense of "being there", and at other times, the overpowering highlights divert attention from the focus of the photo. I feel that often, Indigo's HDR highlights (relative to the subjects) are even more overpowering than the default iOS camera's highlights.
I don't know if there's a way to fix this programmaticly, maybe do some AI subject detection and limit number of HDR stops against median subject brightness? Or add per-shot setting to control allowed HDR stops, alongside exposure, etc.
By @nnhuy
What you are bringing up are legitimate concerns, but the solution is partially always going to be subjective - what is overexposed to you may not be to someone else and vice versa. Indigo team will continue optimizing our AI model which analyzes the image and computes the SDR and HDR "looks", and one way to improve it is to simply add more manually edited scenes in the training dataset where the bright highlighs are appropriately amplified or reduced.
@BorisTheBlade I upgraded to the 17 pro max and can't wait for the teams updated app to offer compatiblity. I want to ask you and the team about what they thought of the new pro series in terms of the accessiblity to the API information from Apple this year? Is it more or less the same as last years iterations or is the team able to access more to be able to build more features to Indigo? From just the stock aspect side of things, I can definitely see that telephoto is massively improved due to the new sensor. As general, the stock photos are still oversharpened, but much less than previous gen, the proraw to me is MASSIVELY more improved this year, as it's not overly baked with sharpening, noise reductions, and crushing of shadows are not pure blacks as if you use the stock photos editor, set shadows and contrasts to -100 it will give hazy looks (which it should) and expose the shadows properly.
It will be great if Indigo can give insights and thoughts! I'm always eager to learn from the devs.
By @nhan_8084
We are working full steam on enabling Indigo for 17-series, so we haven't yet done full eval on the quality of the native camera ProRaw and HEIC captures. From the API perspective, the improvements do not come from new devices but from new SW, and iOS 26 offers a few new APIs which we will find very useful. Two most interesting ones are continuous background execution (so Indigo can finish processing images in the background more reliably) and region of interest specification for auto-exposure and auto-focus algorithms (when we use pinch to zoom to crop the center of the sensor area, the region of interest for taps was NOT reducing so far, causing focus and exposure issues). We'll introduce those to Indigo in the coming weeks.
@BorisTheBlade when you mention pinch to zoom, I envision you meant the digital zooms, and not the SR range of 2x, or 10x correct? Will this region of interest specification for auto exp and auto focus helps improve/make the focus stacking or expo stacking in any ways?
By @nhan_8084
I mean any pinch-to-zoom with digital cropping - this is irrespective of our super-resolution. If you zoom in digitall and then tap to expose/focus, currently that doesn't always work well. With this update it "should" work better (testing notwithstanding).
Please explain what is happeining to the faces of the artists. I'm using an iPhone 16 Pro Max. This is about a 5x-8x on the camera. There is a lot of distortion. I was shooting in manual mode, the screen shot is taken from LR. This is the reason that I want to use indigo. I like to shoot in manual mode. Thx, Steve
By @steves75674135
Hi Steve - thank you for sharing these. This is a decently low light scene with moving subjects, and it looks like the algorithm for aligning and merging multiple frames to reduce noise is merging some pixels it shouldn't. I will pass these results to the team and we'll work on tuning the algorithm further. It does get tricky however because each individual frame is quite noisy (ISO is high and exposure is fast at 1/800), and merging such frames creates a problem of differentiating between signal and noise.
AdChoices
