Forum Replies Created
-
Posts
-
Nitro uses the Photo library, and the Photo library only offers an “estimated” count. So, I could show that, but it would not always be correct. It’s possible to get the actual count, but that would impact performance. I will make a note – perhaps it can be added as a preference (with a note about performance).
Photos defaults to “JPEG on top” and has a feature in Edit to switch to the RAW on top. The file name Photos shows is always the JPEG, even when it’s showing the RAW.
Nitro defaults to the RAW, though it shows the JPEG image, since that is what Photos provides to it. In contrast, it always shows the RAW’s file name. It also has a feature to switch to the JPEG when editing.
So, both can edit either half of the pair. Photos is JPEG centric and Nitro is RAW centric.
If you want to switch in Nitro, the button is to the right of the “four way control” and right below the histogram. It only shows up if you have an R+J pair in Edit.I was able to get some more information about these files. They are indeed ProRAW files. The JPEGXL part is just the way they are compressed to save space. Yes, they also contain a JPEG as the preview.
These are weird files. They act like ProRAW images – my code shows the sliders for ProRAW (and regular RAW) and they seem to work too, so….hmm.
These files do NOT work on earlier OS versions (Ventura, for example is not supported).
This will no doubt cause a lot of havoc as people take shots with their new phones and cannot open them on their older Macs and devices.It’s not a RAW file, and it’s not a ProRAW file. It’s relatively new file format that is intended to replace JPEG. It seems that Apple is using the DNG format to hold the JPEGXL data (since DNG is a general purpose container and not a RAW-specific container). At this point I don’t have any tips – it should just work.
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.
