Forum Replies Created
-
Posts
-
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.
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.
