701
Replies
@BorisTheBlade I took a 2x SR and 10x SR on a scene with foliages to see how it handles fine details and I noticed some weird things. Either the merge didn't align right, or the fill AI didn't apply right bc there seems to be random radial blurring like faux bokeh look. Almost like bad portrait mode bokeh. I will attach raws for inspection, the SOOC jpeg, and crops of the issue place in lrm.
By @nhan_8084
Foliage is notoriously challenging, because it is very high frequency content which is rarely static. Together with camera shake, alignment errors are hard to avoid. This is a high priority image quality improvement for the team, so we'll be working on improving the results in the upcoming releases.
Here I want to share the night scene that my friend took in Japan. The Indigo camera is really great.
However, the problem is that sometimes it takes a quiet long time to open, or even just freezes. This problem has only recently occurred on my iPhone 16 pro max.
By @realrev_
This is a very nice photo - thank you for sharing! Regarding the app seemingly slowing down, a couple of questions: did you by any chance update your OS on the device? We have noticed issues with some iOS 26 beta versions (e.g., beta 6), so that could be a part of it. Second question is whether you rebooted your device recently? It can help sometimes. If the issue persist please reach out again and we'll debug further.
There is a bug whereby if you Reset Edits in LR on an Indigo DNG, the Profile changes from 'Indigo' to 'Adobe Color'. I was hoping that this would be fixed in the latest LR 8.5. Is this a bug that needs a change to LR to fix or is it an issue with the DNG that needs an update of Indigo to fix?
By @leed24280355
This is a bit of a tricky question, as there are several versions of the DNG that could be used when the user wants to reset. Two most important ones are a version as intended by the camera (i.e., with the Indigo profile and with other rendering preferences set by the camera), and what the user's default rendering settings are. So when you click on 'Reset' the system cannot know which version you want to see. That is why there are several resetting options in ACR and Lightroom like "Reset to Default" and "Reset to Open". A recommendation when editing is to save versions, so you can always go back to a version that is meaningful to you. Others on the forum may have more helpful suggestions.
I have just discovered that if you import an Indigo DNG into LR Mobile, then go to LR (cloud) version on the Mac, open the image and then use the option 'View/Show Original' (also obtained by pressing and holding the \ character), even if no edits have been made at this point, the image will change to 'Adobe Color' profile. It's almost as if the DNG was actually imported with the Adobe Color profile and then changed to 'Indigo' automatically on import.
By @leed24280355
This goes back to the question of "what is a raw photo", which is in truth a philosophical question. To your specific point, "Original" may to some users mean "out of the camera", but to others it may mean "raw pixels + minimal processing". To be more precise, how Indigo DNGs are actually formed is as follows:
- Raw pixels are stored as pixel data (computed using Indigo's computational photography)
- Indigo profile is stored as metadata in form of tone and color Look Up Tables (LUTs), called PGTM and RGBT.
- Additional rendering preferences are stored as metadata, including exposure compensation, denoising and sharpening preferences, etc.
Here, number 1 is technically the "Original". You cannot of course just show those raw pixels without some minimal processing, so Lightroom does demosaicing and other post-processing steps as defined by your default camera settings. And 1+2+3 is what would be for "Reset to Import". Hope this helps a bit.
So Indigo DNG is just the bullet point number 1 right? Bullet point number 2 can be negated if chosing Adobe Standard right? Bullet point number 3 should not be existing in the DNG bc that's considered baked processing like ProRaw, but not Indigo raw right?
By @nhan_8084
This is partially correct:
- Point 1 is the raw pixel data (after the computational processing pipeline of aligning and merging multiple frames is completed), which is stored in Indigo DNGs without any additiona adjustments.
- Point 2 is the core of the Indigo "look", which is what is the main point behind the Indigo profile (tone and color LUTs). This is stored in the Indigo DNG as metadata and is easy to override by changing the profile to, e.g., Adobe Color.
- Point 3 is additional guidance for the image viewer on how to render the raw pixels stored in the DNG, e.g., how much to sharpen, denoise, brighten/darken, etc. This is metadata which is ALSO stored in the Indigo DNG. But this can be overriden in Lightroom/Camera raw by moving the editing sliders. None of this metadata is baked into the actual pixels.
If you open an Indigo DNG in another raw viewer/editor (e.g., in Apple Photos) the image will look drastically different than it looks in Indigo or in Lightroom. That is because they ignore points 2 and 3 completely, and only use the raw pixel data + basic capture metadata (like exposure time, for example) they do their own rendering.
With Indigo DNGs:
- There is no option on the Profile drop-down to manually reselect the Indigo profile
- If I reset the edits or view original, the original image as imported is *not* displayed because the profile reverts to Adobe Color.
This was all mentioned here early after the release of Indigo and I think the response was that you would check with the LR team to find a fix.
Thanks
Lee
By @leed24280355
I am following up with the Lr team on this, and we'll work on making the workflow better. Stay tuned.
If I use Indigo to take a DNG+JPG and then use LR Mobile to import the images, it will only import the DNGs. The JPGs are not imported to LR Mobile. Is there anyway to ensure that both versions are imported or can this be added as a feature to LR Mobile? I have the same issue when trying to import DNG+JPG pairs created by other apps (such as Halide).
My workaround is to open each DNG+JPG in Apple Photos and use the share option to Edit in Lightroom. That then brings the JPG into LR Mobile but this has to be done one image at a time, which is cumbersome.
By @leed24280355
Thank you for sharing this. Typically users want to import only one of the two, which is why Lightroom for mobile focuses on the DNG workflow. Having said that, one way to speed importing JPEGs is to multi-select several images in Apple Photos and then share with Lightroom. This way, all of them will be shared in one go, instead of going one by one.
I know of one app for iPhone that names the RAW and JPG slightly differently and in this case they appear as seperate files to LRM.
Lee
By @leed24280355
We are working on adding support in Indigo for this. Hopefully that will make some user's workflows easier.
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.
AdChoices
