Forum Replies Created
-
Posts
-
By the way, I checked to see if macOS and iOS have the ability to create JPEG-XL files and unfortunately, the answer is no. It’s not possible either in macOS Sequoia or even macOS Tahoe. Since I rely on Apple’s code to export files (and write metadata etc), that format will have to wait until they get around to adding support. Sorry.
XMP files have an issue, which is that there is no established file extension or naming standard for anything for proprietary RAWs (e.g., ARW, NEF).
For those files, the XMP is the raw file name with .xmp. Simple. But JPEG, DNG, etc. don’t follow that rule. That’s because of R+J pairs. If you shoot ARW + JPEG, then there are two original files and one XMP. Adobe could have specified what to do there, but instead they decided to punt and write the metadata into the original files.
There is obvious risk to modifying original files, and some people are dead-set against modification just on principle (understandably).
Nitro’s current solution is to write XMP for JPEG, DNG, etc. using the format
_extension.xmp, so for DSC1234.JPG, the XMP is DSC1234_jpg.xmp. Unfortunately, no other app uses the convention, so the XMP files are not seen by those apps.
There are only two solutions: 1) use .xmp for those files (which won’t work for any R+J pairs), or 2) write into the original.
My plan is eventually to offer both but not be happy about it 🙂
It could yes. Finder tags are only strings (the colors are separately represented), so as long as no color is needed, it’s possible. However, it’s always tricky to write data when there is another application(s) that are also writing them. For example, if Nitro writes out tags, but then you add/remove some yourself in the Finder, what does it do – you don’t want the apps fighting with each other. By that, I mean, if Nitro writes out tags, and then you remove or add a tag in the Finder and then Nitro looks at the image again – the tags don’t match. Should it update them again, etc.? This is how simple features become complex ones with lots of knobs and switches.
Sorry to hear that. I spent a while trying to get the app to show extra windows, but it worked properly each time.
The simplest thing would be to reset the app’s defaults for window position. You can do that in the Terminal.
- Quit Nitro
- Open Terminal
- Enter the following command, INCLUDING the quotation marks: defaults delete com.gentlemencoders.nitro “PersistentWindowState v2”
- Open Nitro
If this does not work, then execute this simpler command to reset all the defaults (quit Nitro first).
defaults delete com.gentlemencoders.nitro
JPEG-XL is much slower to encode / decode right now. I don’t think there is hardware support for it, unlike HEIC and JPEG which do.
The main issue is that Photos does not read XMP sidecars. I plan to add JPEG-XL export support in the (relatively near) future, which would also embed the keywords into the file, at which point, Photos will be able to see the keywords. The other way for Nitro to solve this is to have Nitro write XMP directly into original files (in this case, the JPEG-XL that you made in the other app). However, that is a bit longer term, as writing into original files has risks that need to be managed carefully.
Sometimes that happens if the app fails to save the window positions and counts. Please close a tab, wait 3 seconds, and then quit the app. Then reopen Nitro. Does that tab reappear? If it does not, then close the other tabs (except for one), wait a few seconds, and then quit / reopen.
I’m sorry to hear that. There is nothing in the new version of the app to delete LUTs (in fact, there is no code at all in the app to delete LUTs). On iOS, if you delete the app, then iOS will delete the LUTs and any other app data, but that’s not something that happens when deleting apps on the Mac. Unfortunately, I cannot explain why this happened to you. If you are able to determine the cause, please let me know and I can try to figure something out.
I cannot see the image, so I don’t know why the tools would have vanished from the right side. If you can email support@gentlemencoders.com with the screenshot, I can take a look.
There are two ways to process a RAW image. One is to “develop it.” This is what Photoshop and Affinity Photo do. They take the RAW, give you some sliders and then the result is a new file (e.g., a TIFF) or a layer. You don’t go back to the RAW again.
The other way is what RAW Power, Nitro, C1, Lightroom, etc. all do. They decode the image when needed and you can adjust the RAW decoding at any point. If you decode with C1, unless you export a file (again, like a TIFF or a JPEG), there is nothing to give to Nitro, except the RAW file. And if it gets the RAW, Nitro will decode it (differently from C1). There is no way to convert a RAW, and then somehow keep it in a RAW format. It has to be converted into another format (as a new file), or decoded on the fly as Nitro and C1 do.
