Forum Replies Created
-
Posts
-
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?
I still don’t understand what you are reporting. You import to a folder using Image Capture and some files are grayed out in Nitro? If so, can you double-click them in the Finder?
Yes, I’m aware of the issue. On iOS, pCloud and other cloud services work by creating plug-ins / apps that connect to Files.app. They are not accessible to apps in general.
There are two cases:
1) You want to access a file in pCloud – no problem – that works out of the box
2) You want to access a folder and its contents in pCloud – big problem.Nitro only accesses folders, because of the need to read and write sidecars. It has to be able to write new files to the folder.
To access the folder and its contents, I have to write special code that talks to pCloud. And then write special code for Dropbox, …
The app has to handle the downloading and such which is more complex because of the sidecars.
I haven’t written all of that code yet, but will at some point. I will start with iCloud Drive and then build from there.
Are you saying that the images copied from the card are not written properly to the Finder by Image Capture? Or is the user interface drawing the thumbnail incorrectly?
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.
