Forum Replies Created
-
Posts
-
A Photos Library on a network share is not supported by Apple, as far as I know. However, if you simply want to browse the images stored in folders, that would be different.
Not all NAS work with Nitro on iOS (Mac seems to be fine in general) – I have tested Synology (which worked) and UGreen (which did not work). The basic symptom is that the app can see the folders, but the contents are reported by the OS as empty. As far as I can tell, this is either a configuration issue or bug in the NAS (since some NAS work fine).
Yes, and Yes.
When editing the JPEG, the edits are applied to the camera-generated JPEG.
If you switch to the RAW, then the edits are applied to the RAW and the look of the camera-generated JPEG is not used.If you are exporting original + metadata, then the edits should be present. Do you see them in the Photos library on the machine you are actually exporting from (but not on other machines)? Trying to figure out if this is an iCloud issue or something else.
@Gary, the app doesn’t work by writing XMP files to the Photos library. I have a different way so that things are properly stored and read by Photos.
Sorting options depend on how the images are stored. When the images are kept in the file system, the app can sort them using information that is immediately available, such as the file’s creation date. It does not sort by rating or EXIF data because that would require opening each file individually, and doing so again whenever the data changes.
In the Photo Library, sorting is limited to the options that the library itself provides, which are based on date (created, modified, or added).
Both approaches work this way because the underlying database — whether it’s the file system or the photo library — can sort far more efficiently than having the user interface manually scan through every image.
I could add additional sorting choices, but doing so would significantly slow the app when working with large collections. I learned this early on while developing Nitro, where I initially included more sorting features but eventually removed them due to performance issues, especially on iPhone and iPad.
I’m not sure I am totally following what you are doing but I will try to answer.
Synchronization of Photo Libraries is handled by Apple, and works using iCloud Photos. Nitro does not have any ability to influence how that works.When you are exporting from the file system to the Photo Library via Nitro, how are you doing that? If you are exporting a rendered image (e.g., a JPEG) then Nitro will make a new file with the edits “burned in” and add it to the photo library. The original is not copied into the library and the edits are not copied either.
If you export the original + metadata to the Photo Library, then Nitro will add the original, all Nitro metadata (including editing parameters) and the full size rendered image to the library. You can edit non-destructively and the edits etc will synch over iCloud if you are using iCloud Photo Library.
I haven’t determined the extent of file management tools for upcoming releases. Probably the first batch will be around R+J and XMP file extension flexibility (and possibly writing XMP into the original).
Having multiple XMP files is possible, but I think it would probably create a bunch of problems. If the point of duplication is to be able to edit an image more than one way, then I have a better approach in mind, but again, that’s in the future.
The short answer is that it’s not implemented yet, but hopefully soon (in a release or two, I hope).
The long answer is that it’s harder than it looks if you are using the Photo Library. Actually, it’s impossible to fully implement Duplicate in the Photo Library. That’s because Apple does not permit third party apps to read/write keywords, titles, descriptions, etc. As a result, I cannot make a new image in the library that includes the titles, descriptions, or keywords you may have added in Photos. I can copy Nitro data, but not Photos data. Argh. So, when I make the Duplicate feature in Nitro, any duplicate made in the Photo Library will be missing that data.
In the intervening time:
1) Finder: Use Duplicate in the Finder – if your disk uses APFS, then the duplicate will not use more disk space
2) Photos: Use Duplicate in Photos – they can make a true copy.There isn’t a feature like what you describe. “Done” is not a concept that the app has – it has no way of knowing when you are done with an edit. Conceivably the app could provide a way to set up a folder or Photo library album that you can quickly move files to (via a shortcut key). Have you seen such a feature in other apps? As far as a “edits since last export” goes, it’s certainly possible, but it’s fragile. You could be working on a project and then have to quickly output a unrelated file for someone and the flag has been reset.
Email me if you need help with this. THe forum is not setup for customer support for problems such as this. support@gentlemencoders.com
Edits should save automatically when you go from image to image, or exit Edit. If you just quit the app, it may not save them. Apple made a change in macOS Tahoe which I still need to figure out a work around.
Thanks – I’ll take a look. The keywords should save when you switch modes like that, so there is a bug somewhere.
No, but you can email it to me at support@gentlemencoders.com.
Joachim, Nitro does not delete previews on its own.
The issue with Hasselblad is that the camera provides very low-resolution previews despite the camera’s high resolution. On the Mac, there are settings that will cause the app to generate high resolution previews automatically. Turn off Quick Preview and/or turn off the setting that makes previews while in Quick Preview. You may need to try combinations of them.
Browsing may slow down when you do that, but the app will build full resolution previews as you view images. You can also use the Build Thumbnails feature to do it in a batch. Most apps avoid this problem by having an explicit Import step, where they will make all of these images before you can work with them. Nitro does not do that – it gives you access immediately. However, for cameras with poor previews, low resolution previews are the downside. But, as I wrote Nitro has features to reduce the issue.
The previews themselves can be large and the app uses a high quality setting when making them, which leads to disk space use. I have considered adding a preference to control the preview quality. Maybe in the future, but I think it causes as many problems as it solves.
The app might not save them as soon as you go to Edit, but as soon as you go to another image or return to the grid, it should save them.
So in general, I do not know of any cases where the app fails to save keywords for a file (eventually)
Can you list a series of steps that does not save the keywords?
