>> How do you know the source image data is in fact in Adobe RGB (1998) rather than sRGB? i'm kind of getting lost in this conversation, but for discussion: if i open a .jpg in Photoshop, use the embedded profile (or ignore any missing profile mismatch and thereby ASSUME/ASSIGN my default working profile) and then ASSIGN aRGB (Adobe RGB 1998) -- and the color then appears correct on my hardware profiled monitor -- i have the confidence in my system and knowledge to presume aRGB was a good move if it improves the color better than any other profile i have available. >> How do you know if the source content was made with or without color management? >> How do you know if the source content was made on a wide gamut display or not? i don't care, it does not matter, i have ASSIGNED a profile that appears correct in Photoshop on my hardware-profiled monitor (wide gamut monitor gamut arguments aside), and i can move forward in my task >> Assigning sRGB may indeed produce a better color appearance on your end than the assumed sRGB profile. that's a bit confusing unless it's a typo, there shouldn't be and difference in ASSIGNING or ASSUMING the same ICC profile in Photoshop, unless i miss your point? >> But it's rather difficult if not impossible to know the appearance of the image, without a profile from the source provider. unless the source provider based his image on a device-dependent custom ICC profile, i can most likely fish around for a device-independent profile to ASSIGN to quickly move forward in my process that's not presuming the original designer had some artistic off-color appearance in mind that i most likely would not miss or second guess if their document was tagged...
... View more