Forum Replies Created
-
Posts
-
Tone Control? Are you referring to the Tone Map that is present for ProRAW files?
If so I made a video a while ago about Tone Mapping that you can view here: https://www.youtube.com/watch?v=LguSpnDoShMThe app maintains a small database with some of that information, which is what I would use for the stats. You are correct that metadata is in general a complete mess with camera files – the camera companies cannot even consistently write the same model name into the files for a given camera – I have seen files from the Canon R6 Mark II that have a camera model of EOS R6m2 and other have EOS R6 Mark II.
Please email me at support@gentlemencoders.com so we can work through this.
Walking the tree is the time necessary to go through all of the files and folders that you want to search against. For an SSD, it’s pretty fast; for a network drive it’s pretty slow. Getting file names etc isn’t slow, but reading the metadata is. The app would need a spinner or something because the preparation time is not predictable or consistent.
It’s an interesting idea. Filtering and searching are similar concepts but with a key difference. Filtering: taking a large set and producing a subset. Searching: starting from nothing and producing a set of matches.
Both take a query and produce a result set, but filtering is starting with the images already visible, while search is starting from nothing visible. The app filters rather than searches because then it’s just hiding images from view and everything else works the same way as if there was no filter.
Nitro stores metadata for files it has seen in a database. However, because the file system can change behind its back, it cannot be sure that the files that it was are still there (or if new ones have been added).
So for a search, it cannot simply consider its database. It would still have to walk the entire tree. It would not need to display all the thumbnails, that’s true.
Then, when there is a match, it would need to find a different way or UI to show the images, since they can be scattered throughout the tree and that would break the assumptions of where the images are coming from. So, that would require a different type of view (in the way that the Finder has a different view when you search there).
Are you shooting with compressed Fujifilm images? If so, the next update to the app should provide better compatibility with DR. This means that images with DR will change in appearance when you open them in Edit.
Thanks for letting me know about that. If it’s such a simple mapping, then I could look into it. I figured the DR would be more of a dynamic range compression, and it was darkening some areas and brightening others, so an exposure change would not replicate it very well. For your test images, if you move either Exposure of Whites, are you able to get the results you want? Also, what amount do you move each slider for these various DR values?
Yes. I have a basic implementation, but it’s a lot of code, so I have put it aside for now, while I deal with other pressing tasks.
I do know of people who use various apps to write GPS into RAW files, so it’s not uncommon. Right now Nitro doesn’t have a feature to add location to an image. If / when I do add that, then where to store it will be an issue – some will want it in XMP (there is a spot for it) or written back to the file.
Thanks for sending this information. I installed the app (though I was aggravated by the requirement to capture location + photo library access, neither of which are actually required for this app).
I see that the RAW images get the tone map slider, which is confusing since Adobe says that the images are “RAW”. I don’t know if that’s just marketing or if they are writing the file in a way that makes Apple’s decoder provide the Tone Map slider. The fact that the slider works, would indicate the former (just marketing), since if there isn’t a tone map, the slider won’t do anything. (As an aside, Adobe also claims that DNGs are RAW which is objectively false. Some DNGs are RAW and some are linearized images. Linearized DNGs are basically fancy TIFFs).
I agree that moving Tone Map to zero is the best way to start with such images.
I have two thoughts on this:
1) if the files are DNG or JPG, then Capture One probably won’t see the XMP files because of the way Nitro names sidecars. You would need to rename them to match whatever they expect. This is not an issue for proprietary RAW (e.g. ARW, ORF, etc.)2) There is no XMP standard for flags (location or values), so Capture One won’t read those either.
