I have a question about PL6. When I process a RAW file in Photoshop, convert the colors from “Display P3” to “sRGB” and save the picture using “save a copy” + “embed sRGB” (to preserve EXIF data), PL6 displays “uncalibrated”, when I open the picture there.
When I open it in PS, it shows sRGB as document profile. Why is that? Am I doing something wrong?
When I save the same picture using “export as” JPEG + embed sRGB, PL6 shows “sRGB”. Please take a look at the screenshot example:
A question in a thread shouldn’t be answered around midnight (local time)!
I wrote something stupid: sRGB is not equivalent to “uncalibrated”, it’s even the opposite! By definition according to the IEC standard, an image file with an embedded sRGB profile is “calibrated”.
If there is no profile, it can be considered that it is also calibrated: it must be read as if there were an sRGB profile.
And finally, if there is any other profile (Abobe RGB, ProPhoto, …) it is considered “uncalibrated”, in the sense that it is not calibrated with the sRGB profile. But normally, if “uncalibrated” is present in the exif metadata, the software should be able to display the name of the embedded profile. It seems that this is not the case here, it remains to be seen why.
Ok. In my example what is the use of exporting in another profile as sRGB? I did export with ProPhoto. the image is different when opened for there’s no conversion from ProPhoto to monitor’s profile. Where is all that color management??
it was just an example to display the problem. The picture in question (a Sony ARW raw file) got through PL6 first (where noise reduction & lens sharpness was applied), before it got processed as DNG file in PS. I didn’t mention it, because it wasn’t relevant to the problem. But thanks.
Thank you Wolfgang, I really appreciate your help! After seeing your example I thought that maybe it’s the combination with my ARW Sony file, that’s why I downloaded a Nikon D750 NEF raw file from the internet.
Sadly even with this file I’m still getting the same “uncalibrated” PL6 info result. Why is this the case?
I will describe my process in greater detail. It would be nice if you or someone else could help me out.
To make it less complicated, I skip the first PL6 step and just open the Nikon NEF file directly in Photoshop.
when I open it in PS, Camera Raw kicks in, with following settings. I have to put all screenshots into one file, because of forum restrictions…
in PS I go to edit - “Convert to Profile” - “sRGB IEC61966-2.1” - OK
“Save a Copy” - “JPEG” & “Embed Color Profile sRGB IEC61966-2.1”
After opening of the JPEG in PL6 it shows “uncalibrated”
I’m on the PhotoLab 6.1.1 build 38 (Elite) version (in macOS). I would be glad for any help.
P.S. When are forum restrictions for new users ending? My answers are being displayed hours later and I’m only able to upload one screenshot for some reason. This is counterproductive, especially for new users with software problems.
You are not going to believe it – and no idea why it is like that
After successfully trying with an *.arw-file from another forum user, I noticed in your detailed description / screenshots, that you converted in PS with rendering intent relative colorimetric. So I thought to do the same … and bingo – instead of sRGB PL now showed the jpg as uncalibrated.
I could not believe it, repeated with perceptual and relative colorimetric, turned black point compensation on and off, did the same thing with my *.nef-file
– everything with rendering intent relative colorimetric showed uncalibrated.
The strange thing is, that all jpgs regardless of their conversion are in sRGB colour space
(shown so in ExifTool → paragraph ExifIFD).
[ BTW, I had to go the DNG route, as the old PS cannot handle those ‘new’ raw-files. ]
Repeated the test now in daylight (and fully awake) with
Synchronize metadata with XMP sidecar files
the same thing.
PS conversion with rendering intent perceptual → PL6 shows the jpg as “sRGB”
PS conversion with rendering intent relative colorimetric → PL6 shows the jpg as “uncalibrated”
Wolfgang, thank you so much for your time and effort! I’m glad you found the exact parameter that is causing it. I was afraid that I was doing something wrong, but “relative colorimetric” seems the default value in (recent) PS, therefore it should be safe to use.
Now I’m just surprised that PL6 isn’t interpreting it “correctly”. Maybe DxO should look into it?..