
Originally Posted by
xpatUSA
Hi Andre,
No need to post the original. As you say, from an original there can be several different output files for different purposes. An oddball example might be sending me a ProPhoto JPEG (it's legal and possible), not that I'm asking you to.
I don't know what editor(s) you use but, in mine, if I set a working space of sRGB, the review image changes to sRGB but the RGB values in the original file do not. So, if I am viewing in ProPhoto working space, highly saturated colors are not usually clipped - by which I mean saturation-clipped - by which I mean hard up against the ProPhoto gamut boundary causing (in some editors) out-of-gamut warnings if you have them enabled. Pardon the long sentence!
Now, if I select a smaller working space, e.g. sRGB, the file RGB numbers still do not change but the color histogram does and also the color-picker numbers do, because you are now looking at how your image would look after conversion or transformation to sRGB. At this point, you can make any adjustment your image needs and when you 'save as' a file for here, it would turn out the same as it appears in your editor review image. (By 'saving as' your original remains unchanged, of course.)
I generally recognize saturation-clipping by areas where one of the RGB numbers is zero. For that reason, I have the low level warning set to 1 (out of 255).
Hope this helps you to overcome flower shots with those false colors - they are fixable.