Hi,
I would like to find out, when I view photos on my Windows computer, why colours look different in different applications.
Would the solution given here fix my problem? https://answers.microsoft.com/en-us/windows/forum/all/why-is-my-photo-viewer-off-color/183f74cd-0db8-48fa-8dc3-5373d3c58596
I do not wish to try the method in case it upsets my settings. If the solution suggested does not work- how do I undo the changes.
Photo look better in Windows Explorer Preview Pane (left) and Topaz Photo AI (right)
Photo look off colour in Windows/Photos (left) and Luminar Neo (right)
The actual photo
@kwongphotographyhotmail-com
Thanks for the information. No I have not done the calibration. After reading your message I did a quick search. It looks like both i1 Display Pro calibration puck and the Calibrite ccStudio are bit expensive.
I think your question had to do with colorspace. In general the largest major one is Prophoto, then Adobe RGB, then SRGB. When working in post processors you have a choice but when sending the photo where you are not sure of what the recipients browser or monitor is capable of the best bet is to export a jpeg with srgb imbedded. Every post processor will have settings for this. While working it's better to maintain the largest colorspace you can and to work in 16 bit mode if you can.. Even if you can't see the changes now on your current monitor, as you adjust you will have more latitude. When you save a jpeg it is always 8 bit but you could have any colorspace. SRGB is a safe bet, but some printing houses will accept Adobe RGB.
The problem arises when you don't imbed a color space in your file. If the viewing software can't figure out what you intended it will use the viewing devices system profile or srgb. If your file is not in srgb the colors might look strange because the viewing software would be treating it as srgb when it isn't. Bottom line, send jpegs with SRGB imbedded and there will be no problem.
https://photographylife.com/srgb-vs-adobe-rgb-vs-prophoto-rgb
While paying attention to calibration don't forget also that different programs read raw files differently, depending on whether they use the camera's embedded JPG settings (as do the Nikon programs, for example), or their own (as I think Lightroom does). I don't do much heavy duty processing, and stick mostly to Nikon and freeware, but notice considerable differences in how a NEF file is initially read into the program. Irfanview, for example, usually reads a file as it appeared in the camera. Faststone, however, does its own exposure compensation and the result often differs considerably.
They will all read a JPG the same, and if that's where the issue occurs, then calibration is likely to be the culprit, but if you're starting with NEF files make sure that the problem isn't in that first reading.
@kwongphotographyhotmail-com Thank you for the information. Much appreciated. I will try to resolve it and let you know