Forum Replies Created
-
Posts
-
There is no simple answer to this question, which is why Nitro offers both options.
Photos organizes R+J as a single “item” which is good and bad (you can’t split the two pieces apart, but you don’t have both images cluttering the grid, etc.)
Even if you don’t use iCloud, there is value in using Photos. You can access the library with multiple apps. If one day, there is enough storage in the cloud, you can use iCloud syncing. you can mix and match editors. You can make albums, etc. If you use the file system, you have full control over storage (where it is and you can split across drives).
Hard to say from your description. You can try the same steps in Preview to see if you get a different result.
There are probably some bugs with stale data in that use case. The app has to rebuild its thumbnails and previews and then update the viewer. It probably does not do that perfectly when the aspect ratio changes.
On iOS, Apple does not provide a way to write tags. I can read them (and do), but that’s all.
I have not looked into the XMP labels – there could be some compatibility issues which need to be figured out.Nitro supports color labels when using the Finder, yes. You have to give the app permission to read the labels [Apple hides them].
Go to the Image menu and pick Tags.
The app does not (yet) have file moving / renaming features.
Unfortunately, I cannot tell what is wrong based on what you have provided. Please email support@gentlemencoders.com so we can walk through what is happening.
Another customer mentioned the issue with file extensions. There are a few things going on here.
Nitro uses .xmp for all XMP files. If it’s a proprietary RAW (that is, not a DNG), then it writes with just the XMP extension. If it’s a JPEG, DNG, etc., then it uses the underscore.
It does that to ensure there cannot be a conflict between a proprietary RAW and a JPEG with the same base name. This can happen a couple of ways. One is RAW+JPEG. Another is a RAW + an exported JPEG stored in the same directory. Or, the JPEG is first imported and then the RAW from a R+J pair. Also, this makes it simpler for the app to know what file goes with which.
The terminology of “.jpg.xmp” is attempting to follow a convention of “two extensions”, but that is supposed to be used in a particular case – when the storage is “layered”. For example, TAR and GZIP. That is usually done as x.tar.gz because it’s a TAR file that has been gzipped. Once you unzip it, you have x.tar.
But that’s not true for a file named “.jpg.xmp.” The JPEG is not stored inside an XMP container – it’s not a layered model.
I will probably add a preference at some point to let sidecars be named with the double extension, though I don’t think it’s correct. If I do that, I would update the “Migrate Sidecar” feature to adjust the names of existing sidecars in a directory. I’m not inclined to have the app search for both files and try to figure out which one to use though. Having two files containing similar data always leads to problems.
Unfortunately, this is one of the many things that Apple does not permit for App Store apps. When apps add images to the library, they are always imported as managed (that is, copied into the library). And since Photos has such weak file management, there is no way for you as the user to make them referenced files.
If you are doing these actions outside of the crop tool, then the app will choose what portion of the image to use for the 3840×2160, and it is probably the left part of the image.
I suggest this instead.
1. Open the crop tool
2. Set the aspect ratio to 16:9
3. Type the size into the text fields
4. Position the crop box.Or:
1. Open the crop tool
2. Set the aspect ratio.
3. Position the box
4. Export but choose a custom size of 3840 x 2160.Thanks for reporting that. It’s a bug and I’ll make a note to fix it.
One way to get out of this is to hit the escape key. It will take you back to the grid and the keyboard should work again.There are many ways to organize (or not organize). Some people have existing keywords and keywording systems. It is a popular request.
Some people use hierarchy alone and that’s enough.
Most people probably will not use keywords (I don’t) and that’s fine. AI can also work but has obvious limitations.
Yes, it’s very frustrating. Apple does this by not providing public APIs for developers to read and write keywords. Instead there are private APIs that are only usable by Apple. Some developers have figured these out. But if an App Store app tries to use those private APIs, the app will be rejected by Apple.
