IMatch is not a RAW converter, it is an Asset Management system. I do not use Sidecar files, nor does Nikon Capture NX2. I believe the reason that the ICC Color profile is not displayed, is that it is not embedded by the camera when the image file is recorded. Straight from the camera the color space tag is correctly displayed in IMatch as sRGB, however no ICC Color Profile is displayed for the image properties. NEF are always of the sRGB color profile, however I have never confirmed this to be true (I just assume).Īttached is a snippet from the IMatch Properties window:Įdit: I just shot a. I believe also that the preview images that are embedded in the. Nikon Capture NX2 does read the applied color space profile tag as tagged, in camera. While there is an "applied" colorspace in the NEF (RAW) file, IMatch does not read this tag, or does not display it when displaying the Image Properties in the Image "Properties" dialog box. Perhaps I was not clear in my statement, I was referring to the Exif properties as viewed via IMatch. If companies are going to advertise compliance of known standards, they should follow them. I just look from time to time to assure I am posting. Perhaps I am being too anal about the whole thing.
This makes me lean towards Capture NX as the culprit as it is not as you stated above, tagging the file correctly. I also attempted to convert to profile, within Capture NX 2, and it also yielded the same results. I am able to select a (custom) icc color profile within Capture NX, but it yields the same result of an "Uncalibrated" ICC Color Profile (I tried using a previous Nikon version as well as IMatch, Epson, and HP sRGB profiles). If I am correct, this is not the first time I have run into this issue. This is why I tend to run into this issue. from time to time I "check" to make sure I am still using the correct web colorspace of sRGB.
The Colorspace "tag" does not show up in the RAW image formats within IMatch, just in the. It is just frustrating at times that a "product" can state that they are exif 2.2 compliant and blah blah blah, then demonstrate that they are anything but compliant These revisions are not "seen" as actual sRGB colorspaces by 3rd party applications due to the name(s) they are given. It seems that as AFX explains that while the sRGB colorspace has not been updated in years, Nikon keeps making revisions. Thank you Jan Anne, I have indeed checked all the custom settings within the application(s).
0 kommentar(er)
