1107
Replies
By @pmattos92
Thank you for sharing detailed observations and suggestions. I'll do my best to comment or answer your questions:
- Getting manual focus right is tricky, I fully agree. The "focus peaking" feature you are mentioning is nee impossible to implement well. Basically, it is impossible to detect "peak sharpness" of a pixel or image region from a single image. You would need to analize the same scene but with multiple images, captured with focus shifting (i.e., a focus stack). Furthermore, this would heavily depend on the amount of noise in the image signal and zoom level. We tried implementing the feature and doing some quality tuning, but basically it ended up not being precise enough to be useful, which is why we didn't ship it and relied on the focus loupe in Pro controls.
- Improving focus and exposure in Auto mode is on our todo list. There are several aspects of it: separating the tap locations for focus and exposure, accounting for the digital zoom (this required changes in iOS which will be available in iOS 26; we will add them then), and adding the exposure compensation slider. All of these are on our roadmap.
- As mentioned in #2, we will add EC to Auto mode in one of the upcoming releases.
- This is an interesting suggestion. We are working on adding support for user-customizable post-processing parameters, but for computational photography this is for now accessible from the Pro Controls. Namely, in Night Mode, the last Pro Control on the right exposes the Frames To Merge slider: the fewer frames one uses, the faster processing will be, and vice versa. We can think about some more high-level app setting, but in truth, with Indigo we are trying to push the limits of computational photography and of iPhone hardware. We have quite a few additional optimizations to try which may limit or negate the need for customizing the amount of computational photography.
Regarding your question, low power mode should not compromize the quality of Indigo captures much, if at all. There may be some impact however, primarily with Zero Shutter Lag captures in Photo mode, where the rate of raw frames the app is able to get from the OS may go down. If there are fast moving scenes, there may be fewer frames to merge, resulting in noisier captures. Other than that, note that in low power mode your display will not show HDR properly, so images may not look good until you disable the low power mode.
By @pmattos92
Regarding your question, low power mode should not compromize the quality of Indigo captures much, if at all. There may be some impact however, primarily with Zero Shutter Lag captures in Photo mode, where the rate of raw frames the app is able to get from the OS may go down. If there are fast moving scenes, there may be fewer frames to merge, resulting in noisier captures. Other than that, note that in low power mode your display will not show HDR properly, so images may not look good until you disable the low power mode.
Clarifying the low power mode a bit. Regarding ZSL capture, we suspect there may be impact on the frame rate of raw frames we may get from the system, but that is not confirmed. In reality, there may be no impact. And on the HDR side of things, the captured images will be processed just the same, it's just that the OS will disable the HDR display output (as it consumes a lot of power) so the images will temporarily look poorer. If you disable low power mode, then those same images will look just fine.
Is anyone using PI on an iPhone 16e? If so, how does it run and what zoom options are available?
Thanks
Lee
By @leed24280355
On 16e the app should run just fine. Since that device has only one lens, the zoom options are 1x and 2x, with maximum zoom being 5x. For the selfie camera they remain the same.
If I set an exposure compensation value via the pro settings in the app, next time I restart Indigo, that EC value persists, even though the app is no longer in 'pro' mode. I would have thought the correct behaviour should be either
- Persist the EC value on restart *and* go back into 'pro' mode
- Stay in auto mode on restart with the EC value reset to zero.
Lee
By @leed24280355
Lee, I tried reproducing this issue but couldn't (assuming I understood you correctly). I tried the following:
- Set the EC to +3 in Pro controls
- Pause or kill Indigo
- Start Indigo
- Observed that the viewfinder may start brighter (it perhaps uses the last used exposure time and ISO values), but it quickly recovers and exposes correctly for the scene.
Are you noticing a different behavior than that? If so, can you elaborate more on the exact steps you use and exactly what you are observing as a result. Thanks
Hi Boris
I can confirm that I see the same behaviour as you. What I think I was observing was that, after a restart of Indigo, it is indeed in auto mode (which is fine) but if you press the icon to go back into Pro mode, you get the same settings that you mave made in the previous instance of Pro mode. So any changes to settings (EC or shutter speed, iso etc) in Pro mode are 'sticky' and are retained for the next time you go into 'Pro' mode.
I assume this is the expected behaviour? It just means that if you don't use Pro mode for a while and then click on the icon for it, you may forget that settings have been made there and retained. Perhaps this is just an awareness thing on the part of the user, one can always do a manual reset when entering Pro mode - to be fair the icons for any changed settyings are highlighted in yellow, so I guess it is easy to see.
Another option is maybe to have a setting that switches on/off 'reset Pro mode settings on restart' or similar.
Lee
By @leed24280355
Lee - correct, this is the expected behavior. The logic behind the decision was simple: if the user is in a session where they capture with Pro Controls on in the same/similar situation, then their selected values should be honored between app restarts rather than forcing them to manually set it every time. On the other hand, if they want to start from scratch, they can long-press on the Pro controls icon and quickly reset all. Having said that, we will be working on adding overall app preferences for which settings should be sticky across app launches vs which should change. This should include which lens to use, which mode to be in, Pro controls, etc.
I have one photo in my Apple Photos library whcih has bad metadata and has 2028 as its date. So after I take a photo with Indigo and click on the photo thumbnail in the bottom left my future dated photo appears instead of the photo I just took. Obviousely a problem on my side but...
iOS 26.0 (23A5318C)
iPhone 16 Pro Max
By @phydie
This is as expected - Indigo is reading the camera roll to find the images for the filmstrip. Under normal circumstances, it is expected that the last image captured with Indigo is the newest, and that will be shown. If you have a photo "from the future", then there is no way for the system to know that is not what you want shown. We are working on adding album support for Indigo captures which may help with this.
Loss of Indigo Embedded Camera Profile after backing up DNG files to iCloud
I’ve noticed an issue with the DNG files captured using the Indigo Project app. On the iPhone/iPad, these files correctly carry the embedded profile Indigo Embedded Camera Profile.
The problem appears after backing them up to iCloud:
Once downloaded again (either to a computer or even back to the same device), the embedded profile is no longer present.
When importing into Adobe Lightroom, instead of loading the original Indigo profile, Lightroom defaults to Adobe Color or sometimes Apple RAW.
This results in noticeable color shifts compared to what the Indigo app originally captured.
Is there a way to preserve the Embedded Camera Profile during iCloud sync?
By @Juan_Batiz4360
Thank you for reaching out with this problem. We tried to reproduce it by backing up Indigo DNGs to iCloud directly and we found no issues: the DNG structure is fully preserved, including the profile. However, if we use Apple Photos app to back images app, then we see the problem you are describing, so it seems that the cause of the issue may be with Apple Photos app - is that how you are backing up your DNGs to iCloud? If so, try switching to backing up manually or through another mechanism, and we will follow up with Apple on this issue.
Further to the issue o losing the Indigo profile. This time I am using Lightroom Classic and, having transferred a DNG to my hard drive, I import it into LR Classic. I see the Indigo profile as expected.
If I immediately click the 'Reset' Button at the bottom of the Develop module, the Profile changes to 'Adobe Color'.
If, instead, I go to the history panel and click on the 'Import' line, the Indigo profile does re-appear. So, in LRC I can get it back via the history panel but in LR Cloud, there is no history panel in which tgo do this.
Lee
By @leed24280355
Hi Lee, we are following up with the Lightroom team and will try to get the treatment of Indigo inside the Lightroom ecosystem sorted out asap.
Any news on Android development?
By @julian98A2
Android is on the team's roadmap, but further development on iOS is the current priority. We have a lot more computational photography to add and feature to build around them, focusing on a single platform is necessary for the time being.
As I follow this thread, have noticed many experiencing color consistency issue. When exporting the Indigo raw using LR Moibile, I then export the DNG to my Mac. I color grade the DNG in CaptureOne, my editor of choice. I've found that the unadulterated Indigo raws then require me to very heavily color grade the raws back to what would be considered normal.
Using this method, which takes a s - - t load of time, there are zero profiles or settings in the raws to work with. Very tedious but to me, it almost feels like a piece of art when I process the graded raw to a final image file. Just like the old days!
If I don't want or need t take the time, I just use the jpgs for down-and-dirty results. In this reply, I attached a very heavily graded pic of my home town. The original raw was very flat, and looked quite underexposed. Took me 30 minutes to grade, color correction +saturation, contrast and lots of selective masking. The final image file looks like something I could've captured on my Sony A7rV. Indigo is a fun camera app but to me, requires a lot of back-end color grading to make images look super.
By @chrisd40442477
I am not sure I fully understand your workflow. In order for me to help, it would be good to know exactly:
- How you are getting Indigo photos to Lightroom (and which version of Lightroom are you using)?
- How are you exporting the image from Lightroom?
Since you are using CaptureOne for color grading, note that they most probably do not support the full DNG standard, which includes tone and color look up tables. Indigo uses both, and without them the image will indeed look flat. I am curious if you see a similar issue with DNGs opened in Lightroom, or if this is a problem when you workflow uses non-Adobe tools.
I finf that images shot and edited in Pi end up with a magenta tint in the saved file. Is there a way to avoid this outcome?
Also, could the app clarify whether the editing in Pi is applied to to the dng, jpg or both?
By @David 101
To clarify - is the magenta tint there when you edit an Indigo image in Apple Photos, or some other tool? If it is Apple Photos, then this is a known issue. Apple has fixed it as of iOS 26 Beta 4, but they will probably not be back-porting it to iOS 18.x.
Regarding the second question, which file gets opened depends on the path you take to open it. If you are capturing JPEG+DNG, then:
- If you click on "Edit in Lr" in Indigo's filmstrip, a DNG will be opened in Lightroom mobile app for editing.
- If you go to Apple Photos and edit an image, a JPEG will be edited.
- If you share an image from Apple Photos to Lightroom, a JPEG will be opened, NOT a DNG!
We are working on enabling DNG-only capture, as well as saving JPEG and DNG as separate files, so you can see both on the camera roll and decide which one you want to work with.
AdChoices
