Forum Replies Created
-
Posts
-
I have never seen that. If you can figure out what makes it happen, that would be very helpful. If you see it again, tap on the viewer area to see if comes back. Maybe it’s in some full screen La-la land.
I do not see that problem with panning. If I am zoomed in already, then I can move the image by using one finger on the mouse, or two fingers on the trackpad. If you flick (move your finger very quickly) and it hits the edge of the image, then it may jump to the next image, but panning seems to be okay for me.
I understand, but printing is a black hole. Even something “simple” like a contact sheet is full of various landmines with color proofing and the like. I won’t say ‘no’ for sure, but it’s not a high priority.
I see what you mean. Maps scrolls the opposite way from Nitro, but assistive zoom (I can use control + scroll to zoom into the screen), works the way Nitro does. So, there isn’t a hard and fast rule (at least not one Apple follows). I’ll add a preference in the future.
You can send one to the support email address. I recommend scaling it down first so it goes through the mail servers. Nitro reads and writes the dc:subject XMP entry which is the standard place for this. Lightroom has added a place in their own namespace for hierarchical keywords, but that is for true hierarchy (as opposed to the organizational hierarchy that Nitro uses).
Nitro already supports Finder tags when using the file system. However, Apple made changes in Tahoe that I had to deal with.
If you tag an image in Nitro, it writes the tag to the Finder. If you tag in the Finder, the tag appears in Nitro. The tags and colors that Nitro uses are the ones you have set up in the Finder.
The app could write keywords as tags, but that would be a different feature which would not be using the tags you have in the Finder. My point is that the simple case is easy to do, but there are edge cases that get a little strange. For example, if you have a Finder tag called “Portrait” and it’s green. You keyword an image with Portrait. Do you want the green tag in that case, but the other keywords wouldn’t get colors assigned? I’m guessing yes, but I don’t really know.
By the way, I checked to see if macOS and iOS have the ability to create JPEG-XL files and unfortunately, the answer is no. It’s not possible either in macOS Sequoia or even macOS Tahoe. Since I rely on Apple’s code to export files (and write metadata etc), that format will have to wait until they get around to adding support. Sorry.
XMP files have an issue, which is that there is no established file extension or naming standard for anything for proprietary RAWs (e.g., ARW, NEF).
For those files, the XMP is the raw file name with .xmp. Simple. But JPEG, DNG, etc. don’t follow that rule. That’s because of R+J pairs. If you shoot ARW + JPEG, then there are two original files and one XMP. Adobe could have specified what to do there, but instead they decided to punt and write the metadata into the original files.
There is obvious risk to modifying original files, and some people are dead-set against modification just on principle (understandably).
Nitro’s current solution is to write XMP for JPEG, DNG, etc. using the format
_extension.xmp, so for DSC1234.JPG, the XMP is DSC1234_jpg.xmp. Unfortunately, no other app uses the convention, so the XMP files are not seen by those apps.
There are only two solutions: 1) use .xmp for those files (which won’t work for any R+J pairs), or 2) write into the original.
My plan is eventually to offer both but not be happy about it 🙂
It could yes. Finder tags are only strings (the colors are separately represented), so as long as no color is needed, it’s possible. However, it’s always tricky to write data when there is another application(s) that are also writing them. For example, if Nitro writes out tags, but then you add/remove some yourself in the Finder, what does it do – you don’t want the apps fighting with each other. By that, I mean, if Nitro writes out tags, and then you remove or add a tag in the Finder and then Nitro looks at the image again – the tags don’t match. Should it update them again, etc.? This is how simple features become complex ones with lots of knobs and switches.
