Forum Replies Created
-
Posts
-
As far as a thread pool goes, it’s not that simple. Apple’s RAW decoder uses the GPU, so decodes will compete with image loading and editing, and GPUs do not have great tools for scheduling and priority. Decoding also causes memory spikes. On iOS, that will cause iOS to kill the process. These are not simple problems.
Unclear on your question about updating all RAW images without selecting them. No, you have to select them, or use the other setting which will update thumbnails as it goes. In your case, selecting a bunch of images and building thumbnails is likely to work best for you.
As far as prompting people if the thumbnails are low quality, yes, I suppose so. I tend to dislike mysterious-sounding dialogs or having the app behave in different ways based on the image type (e.g., it could see you have crappy thumbnails and then update them) because people won’t understand why some images update and others don’t. And no one reads alerts.
Nitro reads thumbnails and previews from the RAW file. Many camera manufacturers produce substandard thumbnails and previews. For example, Hasselblad is infamous for its tiny preview for gigantic sensors. Sony historically also produces needlessly small embedded thumbnails / preview.
You can see the size of the embedded preview by using Exiftool.
This is what I get for a Sony A7R3 (42 megapixels) – the preview is 1.7 MP. That’s bad!
Full Image Size : 7952×5304
Preview Image Size : 1616×1080Lightroom does not have this problem because it requires that all images be imported. During that process it replaces the thumbnail and preview with its own rendering. But that import process takes time. Nitro avoids import entirely and just reads the files. The downside is that it is reliant on having a decent thumbnail / preview from the camera.
There is a solution to this. You can do one of two things (short of using a camera that produces decent embedded images)
1) Select the images and use Build Thumbnails. That will take some time, but it has to open each image and process it.
2) Go into Nitro Settings and turn OFF “Quick Preview” and also turn ON “Update Thumbnails in Quick Preview”. The app will then replace thumbnails as it goes with the RAW rendering.Of course, you can do both.
These are not the default because rendering thumbnails from the RAW slows the app down.
Jock, my feeling are not easily hurt, so your comments did not bother me greatly. However, I would say that you seem aggravated and that tone did seep into the post. And despite your statement, “I was pointing out a scenario they apparently didn’t consider and haven’t addressed,” I have both considered and (attempted) to address it.
I hope these features in the app help with your workflow.
Hi Jock – sorry to hear you are having these issues. It certainly sounds frustrating. I am unclear on some of your terms. What is a “proxy?” Are you referring to thumbnails in the grid, or larger images in the viewer?
As far as updating, are you referring to decoding of the RAW? and if so, updating how? Do the thumbnails need to be re-rendered for some reason? What’s wrong with them?
What camera(s) are you using? Does this also happen with JPEGs?
It would be lovely indeed. Unfortunately, it’s not a simple matter.
Adobe does not document how their algorithms work, nor do they document what the parameters in XMP stand for. Here is a part of an XMP from Lightroom.
crs:Exposure2012=”-1.61″
crs:Contrast2012=”0″
crs:Texture=”-50″Apparently, some algorithms changed in 2012. Even Exposure and Contrast. From what to what? What is “Texture” (mathematically)?
Further, Nitro does not have all of the adjustments that LR has – so all of those would have to be created from scratch AND match theirs.
It’s like translating Italian to English. The letters are the same, and the basics of sentences and grammar are similar. But it has to be done without a) a dictionary, b) anyone to talk to c) how to detect idioms.
Not impossible, but impractical without spending essentially an unlimited amount of time. There are apps like Avalanche that make an attempt, but even they only convert a subset of adjustments, and not perfectly.
So, the problem turned out to be a known issue. There is a bug in macOS / iOS when an adjustment is present in both a mask and globally. Apple has given me a few ideas for ways to work around the bug, which I have not had a chance to look into, but I will.
Apple’s decoder does not read that information. The other (larger) apps sometimes read that data and get help from the camera manufacturer to process the image.
I am not aware of Photomator doing it since it also uses Apple’s decoder. It’s possible that they read a few fields – can you tell me specifically what they can read?
Karl’s comment about the LUTs is also valuable – I have some Fujifilm simulations in Nitro (they are not official – I made them by hand).
Standard Raw Development turns off as many of the Apple decoding parameters as I can. You can do it yourself by moving the sliders and also turning off Lens Correction (and I think) gamut mapping.
Michael, please email support@gentlemencoders.com so I can help you. When we get a resolution, one of us can post here.
I would need more information to tell you what’s going on, but there is a bug in macOS / iOS that affect Nitro with masks. Specifically, if you have the same adjustment (e.g. Curves) in the main interface AND you also brush Curves, then the system gets confused and it applies to the whole image.
To troubleshoot this, take a simple JPEG, make no edits and then apply a mask with Curves. Do you see the same problem?
I might be able to dim out the drive or something, but I’m not sure. The way iOS deals with drives is crazy-making for developers.
