Forum Replies Created
-
Posts
-
The app does not have synonyms or a way to note them. I can put it on the list for consideration but I can’t promise anything.
Hi. Sorry to hear about this issue. Can you send a screen recording of this happening to support@gentlemencoders.com? That will be much easier to troubleshoot. Also, if you can turn on “Show Touches” in the app’s settings, it will be easier for me to follow what you are doing.
I will have to look into it. If you pick a child keyword, and it adds the parents, then I presume you want the parent keywords to appear before the child keyword in the XMP file?
Thanks for the compliments! Unsure what you mean about the local adjustments being weak – almost all of the global adjustments are available as local ones. Nitro does have edge aware brushes. It does not have control points etc. which are protected by patents (I don’t know when those expire).
Editing of single files was added to Nitro several releases ago (on the Mac). You can use Open… or drag a file to Nitro’s icon, etc.
I have received some reports about NAS issues with iOS / iPadOS, but the same NAS works fine with the Nitro on the Mac. Personally, I have found that a Mac mini acting as a server works fine with Nitro on iPads, so that could be option 4 – use the Mac mini as a file server / turn on file sharing.
Otherwise, of your above options, I would agree that #3 is your best bet given that your LAN is fast, but your WAN is slow (and iCloud is squirrely).
The external disk could be okay too – it could be backed up regularly by setting up a backup script / service on your mini and periodically taking the drive back to the Mini, where the backup system would then run.
GPS is supported in proprietary RAW files and DNGs, so it’s fine to use a tool like ExifTool or maybe HuodahGeo to insert the data.
It’s best to add the GPS data BEFORE you import it into an app / view it / otherwise manage it, because adding GPS can change the capture date / time which can confuse apps that are not expecting that to change.
Tone Control? Are you referring to the Tone Map that is present for ProRAW files?
If so I made a video a while ago about Tone Mapping that you can view here: https://www.youtube.com/watch?v=LguSpnDoShMThe app maintains a small database with some of that information, which is what I would use for the stats. You are correct that metadata is in general a complete mess with camera files – the camera companies cannot even consistently write the same model name into the files for a given camera – I have seen files from the Canon R6 Mark II that have a camera model of EOS R6m2 and other have EOS R6 Mark II.
Please email me at support@gentlemencoders.com so we can work through this.
Walking the tree is the time necessary to go through all of the files and folders that you want to search against. For an SSD, it’s pretty fast; for a network drive it’s pretty slow. Getting file names etc isn’t slow, but reading the metadata is. The app would need a spinner or something because the preparation time is not predictable or consistent.
It’s an interesting idea. Filtering and searching are similar concepts but with a key difference. Filtering: taking a large set and producing a subset. Searching: starting from nothing and producing a set of matches.
Both take a query and produce a result set, but filtering is starting with the images already visible, while search is starting from nothing visible. The app filters rather than searches because then it’s just hiding images from view and everything else works the same way as if there was no filter.
Nitro stores metadata for files it has seen in a database. However, because the file system can change behind its back, it cannot be sure that the files that it was are still there (or if new ones have been added).
So for a search, it cannot simply consider its database. It would still have to walk the entire tree. It would not need to display all the thumbnails, that’s true.
Then, when there is a match, it would need to find a different way or UI to show the images, since they can be scattered throughout the tree and that would break the assumptions of where the images are coming from. So, that would require a different type of view (in the way that the Finder has a different view when you search there).
