Forum Replies Created
-
Posts
-
Many cameras are not supported by Photos and Apple’s decoder. I have a special (unique) way of extending Apple’s decoder, but it only works in Nitro.
So, if you view an image that is not supported by Photos, you usually get a blank thumbnail, and an error in Edit. However, Nitro can both display the thumbnail and edit.
When you save the edits, Nitro saves a new JPEG into the library with the edits. That you can see in Photos.
You may want to read this article I wrote some time ago. It explains some of this.
The interface has a checkbox at the bottom of the preset UI: “Replace Edits with Preset”.
If that is checked, then presets will replace all current edits on the image. If it is not checked, then it will apply the preset on top of the edits. Undo and Redo work to restore the state before and after the preset was applied.
Are you using the Photo Extension? If you are using the Photo Extension on iOS, then unfortunately, Apple does not support the use of RAWs in Photo Extensions on iOS. I have asked Apple’s engineers about this year after year, but nothing has come of it. I suggest using Nitro on iPad as an app instead, which will get the RAW data. You can switch between RAW and JPEG in Nitro in Edit. There is a little button below the histogram that looks like an R on top of a box.
Your images did not come through, just the URL. I opened the file myself. I can see the image looks very flat in the standard rendering (and in Preview), and nicer with the standard rendering off, which is backwards. The culprit is the Boost slider. If you open it with the standard rendering and move Boost to 0.0 the image looks better, but I would not expect that behavior. I can file a bug with Apple if you like, but I will need your permission to include your photo with the bug I file with them. I don’t know if they will fix it, but if we don’t file it, there is no chance they will fix it.
There is a specific bug when removing the sidebar or resizing the window where the scroll position is lost. That’s a bug in Apple’s code, which I have proved. If you have other cases where the app loses the scroll position, I’d like to hear about them.
This is a bug in Apple’s code. I was able to create a reproducible case using one of their own sample apps. I filed a bug with them some time ago. Hopefully they fix it.
Nitro will decode the image in Edit. In some situations, it will decode it while you are just viewing it. It depends on the state of the “Quick Preview” preference. If Quick Preview is OFF, then it will decode the image before Edit (which is a lot slower).
That is hard to say from just this description. However, what I can say is that there are multiple versions of DNG support in Apple’s decoder (at least two, and I think perhaps three). Older DNG files will be locked to an older version of the decode, which is worse than the current one.
One way to tell is to look at the Nitro’s RAW adjustment to see what sliders are present. If it’s an older DNG then you may only see a Gamut Mapping checkbox. For newer decode versions, there will noise reduction and other sliders.
If you have an image with the older decode, one simple thing you can do is to upgrade the DNG version. You can do that in DNG Converter – point it at your old DNGs and make sure to set the latest decode version (of course, do this on a copy of your older DNG). Then open it in Nitro and see how it looks and what sliders are present.
RAW images without any processing will look flat. They are generally sharp. however.
Most RAW decoders will add some processing in order to make RAWs look pleasing to the eye, Apple’s included. Nitro has a preference that allows you to turn that off and get a more “raw” looking RAW image.
Hi,
I’m sorry to hear of this problem. I tried your steps (slightly cropping an image), but the image remained sharp after leaving crop. That said, the forum is not the great way to troubleshoot problems (it’s public, you can’t post images, etc.), so please email support@gentlemencoders.com so that I can help you more efficiently.
Boost is already part of Auto Enhance. When an image is overexposed, then it adjusts Boost to recover highlights better. Setting the default strength to 0.5 for all images would not be desirable in many cases. Tone Map is not currently employed in Auto Enhance, but it’s a good idea. I will see what would make sense to do. Andy Hutchinson seems to have more experience with Adobe’s RAW controls, than the advanced ones in Nitro that are optimized for Apple’s decoder. Frankly, many of his criticisms were simply baffling.
It’s a bug in the app. It’s the app’s job to move the box out of the way when the keyboard appears. I’ll make sure it gets fixed. Thanks for reporting it.
