Forum Replies Created
-
Posts
-
Yes, I can see the value of having the metadata in the grid. Something for the future at some point. What makes it tricky is that the original image is not always present on the device, and the way to access files in the Finder / Files.app is quite different from the Photo Library. Not insurmountable, but there are a number of edge cases.
Nitro does not currently have the ability to search and filter in the way you are describing for the file system. It can filter for flags in the current view which can have subfolders (but is limited in depth at the moment – I would like to remove that limitation). What I am explicitly avoiding is making a parallel to the Photo Library, with a complex database and where features like albums (and smart albums) etc are present on both sides.
I can add it to the list of customer requests I keep, but I can’t promise anything. Each of these systems have separate ways to work with them. My priority is to get iCloud Drive working first.
I’m not sure why it would be blurry either. Are you saying that JPEGs are blurry and also RAWs, or just JPEGs?
In any event, for this kind of thing, it’s better to just email me at support@gentlemencoders.com.
That way you can share images, and we can do a much faster troubleshooting turnaround.The RAW Noise Reduction in Nitro runs in real time. The AI Noise reduction will not run in real time. Unfortunately, I don’t have an ETA on it. Still in the research phase..
The app currently has two preferences for crop. The first lets you decide if the crop always start with the original aspect ratio. That setting is ON by default. If you turn that off, then it will use the last aspect ratio for the next crop. So do a freeform crop and then the next image will start with a freeform crop.
The second setting controls if the crop automatically rotates for the orientation of the image.
Sorry to hear about this bug. Unfortunately, I am not able to reproduce it – I made a subfolder of presets and arrowed back and forth but didn’t see any errors. Please email support@gentlemencoders.com and we try to figure out what’s causing it.
Yes, I see that issue with the search field as well. I will look into it. Thanks for reporting the bug.
Thanks for your suggestion. It has not been discussed before. I’ll make a note – that said, it sounds different from having keyboard shortcuts for keywords, since you are moving images into albums, but I understand the idea. We should try to get tags to work for you though – please email support@gentlemencoders.com and I can try to help you.
I looked into this some more – Nitro does request that a thumbnail be inserted into the file during export. I used ExifTool to look for thumbnail data but I only found it for JPEGs, not for HEIF8 or HEIF10. Then I exported a new image using Preview, using HEIF and also did not get a thumbnail (according to ExifTool at least). So, it may be a bug in the OS.
Perhaps. The auto enhancement adjustments are designed to work together to produce a nice image, not independently. Also, just to be clear, the checkbox to use Levels is choosing between Levels and Curves – it’s not choosing between Levels and no Levels.
These things are possible, but the point of AE is to be a quick way to enhance images with the intensity slider as the primary way of under or overdriving the effect.
Batch AE is on the list to do.
Apps can choose to store a thumbnail or not when making files. If no thumbnail is stored, then the Finder will usually make one on its own if it’s a format that the OS understands. I’ll make a note to try to reproduce it, but the fact that it only gets a thumbnail occasionally is odd.
I’m not sure what you are asking. You want the vertical interface from iPhone also available for iPad? But does that actually solve your problem with Curves / Split toning on iPad? (perhaps you only have the issue with vertical screen orientation?)
It is a bit risky, since there is no approved way from Apple to tag files in this manner. On the Mac, Apple has moved the file (and the format of the data) repeatedly which has been a huge hassle for us as 3rd party developers. There is always the chance they will lock it down somewhere we cannot access but hopefully not.
