Forum Replies Created
-
Posts
-
Thanks for your suggestions. I have made a note about the auto enhance. Applying auto enhance outside of Edit is a complex change (in Photos, you can see it actually has to display a progress dialog because of the extra steps required to “edit outside of edit”.
As far moving Crop, I think that would be poorly received by many people – they already complain to me that Auto Enhance is not in the same area with the sliders. There is a good reason why Auto Enhance is not with the sliders, but I will think about it.
It might be possible. The share system on Mac is a little finicky. The reason the feature isn’t there is because on the Mac, you have full access to the file system. So since you can output the original + metadata to a folder, then moving that to another app is simple. On iOS, that’s much more difficult / requires more steps. Perhaps I’m missing something – can you tell me why the copy to a folder and then open that in another app is a significant issue (other than it’s an extra step).
Right now, when you are not in edit and zoom in, the app typically uses the embedded JPEG. I plan to change it so that it will use the RAW when you zoom in, but of course, that will slow things down considerably.
Sorry to hear about this issue. When you are looking at the image in Nitro, are you in Edit, or not in Edit? I cannot tell from the screenshot. If you go into Edit does it become sharp?
I’m glad you liked it. Yes, making these is a ton of work, but people seem to prefer watching videos these days which is why I have been prioritizing them.
Could it be an issue with time zones? Are these pictures taken in a different time zone from the one you are currently in? Are they taken late in the day (or very early in the morning)?
If you are referring to the Color Class that PhotoMechanic uses, I will have to think about how to support that. That would conflict with Finder Tags (you could conceivably have both and showing two different color tags is going to be confusing. “Preferences are the solution to everything” and also the cause of many problems and complexity.
Thank you!
If you don’t mind, please write a review for the iPad / iPhone app on the App Store – Mac reviews do not appear for iOS / iPadOS. New apps struggle if they don’t have ratings and reviews because people are not inclined to try them out.Aperture stored that information into its own database. Nitro does not manage a separate database for this information when you use the Finder (it uses XMP files). For the photo library, Apple does not provide a way to read or write custom metadata (or keywords).
If your volume is formatted with APFS, you can just duplicate the file in the Finder. APFS will not use any additional disk space in that case (unless you directly modify the file, which Nitro does not do). Then you can make different edits. That is more stable than using an alias or soft link.
Hi Gary,
It sounds like you have a good technical understanding of how labels work (stored in extended attributes). The app does indeed use the extended attribute API to read and write tags. That is because that is the only API that works on both Mac and iOS.
However, I am unclear about the problem you are seeing. The app is storing the string for the label and it is reading the color + the label name from the system to provide the UI.
Strings are the only way labels work in the Finder (color is not actually stored as part of the file’s tag – just the tag name). Nitro uses the same names as the Finder. If you add tags to the Finder (or change names), the app will use them (you have to quit and reopen the app for it to read those though).
