Forum Replies Created
-
Posts
-
If you apply edits in RAW Power and send the CR2, you will get the CR2 without edits. That’s because there isn’t a way to send edit information between apps (Affinity doesn’t understand Nitro edits and vice versa).
If you send a TIFF (or JPEG, etc.) you will get a rendered image with the edits in Nitro applied.
If you are going to edit in Affinity, then send a TIFF from Nitro and have Affinity replace the TIFF with its own edits.
Image Stacking is not on the roadmap that I put on the website.
Unfortunately, the app doesn’t have a way to restart the trial. If you think you only need a few days, then sign up for a monthly subscription and then immediately cancel. It’s not free, but it’s only a few dollars, and there is no additional ongoing monthly cost if you cancel right away.
Also, if you are running into issues, please email them to me so I can help you. The address is support@gentlemencoders.com.
If you are referring to Photos, I believe it will pair R and J together if it has the following:
1) Same file name with different extensions
2) Same capture date
3) Imported at the same time.If you import just the RAW or just the JPEG, and then import the other half, it will not pair them.
My guess (and it’s only a guess without looking at the RAWs), is that the embedded JPEG from Hasselblad is very small. Nitro uses the embedded JPEG to accelerate performance. I believe you can right-click on the images and choose Build Thumbnails to improve the quality.
I just shot a Process Zero image and compared it to a RAW shot with the built-in camera app. The Halide image is smaller than the ProRAW file from the camera, so that leads me to suspect it’s not a linear DNG (as ProRAW files are Linear DNGs). The Process Zero image looks quite different from the Camera app’s image, so I believe that the RAW is just that. A RAW. I suggest trying the same experiment.
Good question. Nitro (and RAW Power’s) extended RAW function is able to add support for cameras and formats to Apple’s RAW engine. That support only works when you are using one of these apps (it doesn’t add support to the system as a whole, as that is not something Apple permits). This extended support means that you can use all of the same sliders that you do for Apple-supported cameras, including RAW-decoder specific ones.
The control for levels isn’t disabling levels – it’s whether to use Levels or Curves. Only White Balance can be turned off. Are you saying that the intensity slider doesn’t meet the need to dial back the effect (I understand that it dials back everything).
Favorites are a Photo Library concept, not a File system concept. I plan to add Favorites the filter when using the Photo Library. The analog of Favorites for the file system would be Flagged.
Adding a gesture is possible but it may be hard to make one that does not conflict with others (for example a horizontal movement would conflict with swiping from image to image. Or conflict with rating and flagging etc)
Actually, that’s not what’s happening. There is a bug in Levels where it does not set up the Luminance / EqualRGB button correctly. It’s actually in EqualRGB by default. I’ll make a note about that and figuring out some kind of default.
The Auto Enhance algorithm works differently from the one in Levels/Curves as you have found. It’s possible to extract JUST the Auto Enhance curves effect out, but the idea for Auto Enhance is to apply multiple effects together to produce a good result (such as curves + shadows + vibrancy, etc.). I have not looked into doing that, but I can add it to the list for consideration.
