Forum Replies Created
-
Posts
-
Yes, that’s possible. I will put it on the list for a future release. The cache grows to store thumbnails and previews for faster display. You can also clear the cache using the Settings interface (near the bottom).
Nitro doesn’t require a Photos library. You can use images stored in the file system + XMP files for metadata. The Photo library provides iCloud synching, albums, and integration with other apps. I absolutely won’t make my own library database. That’s way more work than anything contemplated in this forum thread.
Still not sure what you mean. If you are asking – if I add a keyword to an image, does it automatically get added to Nitro’s list for future keywords, then the answer is no. You can update the keyword list separately (and organize it) in the Nitro UI.
Glad you got it working. What you did is exactly right. Use the edge brush to capture the edge of the sky and then paint with edge-aware off. I do exactly that in the videos I make for the app.
I cannot think of a reason why that would happen for a JPEG. The thumbnail that the app shows initially comes from the JPEG original. Then, it will load the full size JPEG, but again, there is no processing that happens.
Is it possible you have a camera preset set up in Nitro for this camera? Does it only happen when you are in Edit, or does it happen when just arrowing through images outside of Edit?
Are you adding the keyword in Nitro, or are you adding it with another app? What file extension is the original file?
I was able to get two machines set up with OCLP so I could figure out what’s going on. OCLP does not implement a number of capabilities that Nitro requires (depending on the hardware). So, in version 2026.2, I detect that those capabilities are not present (again, which are essential), and display an alert.
Yes. The app has copy and paste of adjustments. It is described in the user manual. For best results, I suggest copying adjustments from an image, leaving Edit, and the selecting other images and using Paste outside of Edit. Crop is an adjustment.
Yes, all of those would be reasonable things for Nitro. In terms of implementation order, it would probably be #4, #3, #2, and #1. Of course, there are many other tasks and features that are also competing for my time.
I can understand your interest in converting LR edits (and presets). While XMP is a fine format for storing certain types of data (e.g., ratings), the interchange ability is not as great as might appear for editing parameters. This is for two main reasons. First, each app has its own implementation of standard constructs (like sharpening, or contrast). Even exposure can be different. Second, apps do not document their algorithms, so app A cannot easily emulate what app B does.
When ACR or Lightroom write out XMP parameters, these are of little use unless the receiving app can convert those values to its own algorithms (and has the algorithms in the first place). Adobe apps can share code and comprehend their own data which is helpful when staying within Adobe’s ecosystem.
So, without algorithm descriptions or code from Adobe, converting adjustments faithfully is pretty impractical. Here is a small snippet from an XMP file from Lightroom:
crs:ProcessVersion=”15.4″
crs:Exposure2012=”-1.61″
crs:Contrast2012=”0″
crs:Highlights2012=”0″
crs:Texture=”-50″As you can see, the Exposure, Contrast, etc have years attached to them, so they have changed their algorithms over time, and Adobe does not document the algorithms or the range of values. Also, what is the algorithm for “Texture”? Some people have tried to convert these parameters using Machine Learning with mixed success. There is a product called Avalanche that you might look into, though it only handles a subset of LR’s algorithms. In short, I do not have any plans to try to do something similar – it’s far too large of an effort with constant tweaks and infinite bugs.
Better file management including moving / renaming is on the roadmap. Yes, it has also has to properly move XMP files and deal with name collisions, etc. for all of the relevant files. That feature would occur after work to handle RAW+JPEG and some XMP related stuff.
I understand that it’s important to your workflow. As far as “feature requests”, there are many R+J customers who have been asking for R+J specific features and those are important to _their_ workflows. At the same time, customers who shoot proprietary RAW are completely unaffected by this. All I can say is that I will add them when I can.
Please see the other thread you posted on about this for an explanation of why Nitro does not use “original.xmp” for DNG / TIFF / JPEG.
Adobe in their infinite wisdom did not create a standard for XMP files for non-proprietary image files (JPEG, TIFF, DNG). For those files, Adobe assumes that the XMP data will be written inside the original file. Modifying the original file is a non-starter for many photographers, who want their originals to be pristine and there is also always the chance of data loss when writing to a file. Nitro supports the idea of immutable originals.
Why does Nitro not use “original.xmp” in that case? Because of RAW+JPEG. In that case, there are two original files and both would try to modify the same XMP file, causing a collision / conflict. For example, it would be easy to rate the RAW and flag the JPEG (say to mark it for deletion). But in that case, both images would be rated and flagged with the same value as there is only one standard place to store that metadata.
At some point (hopefully not long, but there are always so many requests for features and improvements), I will offer the ability to write into the original file and also to let people use the “original.xmp” for JPEGs. As mentioned, both of these have some degree of danger. And, it is virtually certain that someone will have data loss either due to some corruption, or because they have R+J and don’t understand that “original.xmp” is completely unsupported for that style of shooting.
The approach I have taken is less compatible with other apps, but is by far the most safe, and data safety is my first and foremost priority.
