0.96.4 ignores Interoperability DCF option file for None sRGB Colour space

[pkluo]

Hi,

This is the only issue I have with XnView. No sure if anyone has reported this before or this should be a feature request. Apology if post in wrong section.

On most DSC, if set camera to a none sRGB colour space like Adobe RGB. The jpg file straight out of camera will not embed a ICC profile, instead it will set some EXIF tags instead as substitutes. like this example

[MakerNotes] ColorSpace: Adobe RGB
[EXIF] ColorSpace: Uncalibrated
[EXIF] InteropIndex: R03 - DCF option file (Adobe RGB)
[EXIF] WhitePoint: 0.313 0.329
[EXIF] PrimaryChromaticities: 0.64 0.33 0.21 0.71 0.15 0.06
[EXIF] Gamma: 2.2

Since, there is no real ICC profile in the jpg. and XnView will try to use the default sRGB profile for it(in my case). It will end with incorrect display colours. Yes, I can temporary set Default profile to AdobeRGB,then it will work around the issue. But this is a bit inconvenient. If I noticed the colour does not looks right, then I have to check EXIF to determine the IOP, then set a default profile manually. and switch back to sRGB after for those real sRGB file which also does not has ICC profile. Wonder if XnViewer can add a option like, if see "IOP Index" = R03. then allow user to select a system AdobeRGB ICM profile file. Thanks.

[xnview]

could you send me a sample file?

[pkluo]

Hi Pierre,

Sorry for the late respond. This is a perfect example of those straight out of camera jpg file with a AdobeRGB Color space.

https://user-images.githubusercontent.c ... 4caefd.JPG

Some background information regarding it can be read here. Thanks
https://ninedegreesbelow.com/photograph ... ation.html

[Propheticus]

Bumping this up. The same is still true in version 1.4.5

Images that do not have an embedded ICC profile, but do have an EXIF DCF Interoperability index -that's most if not all straight-out-of-camera JPEG images- are not colour managed.

e.g. an image has "Interoperability Index: R03 - DCF option file (Adobe RGB)" but the Genreal > ICC > "RGB profile used when embedded profile doesn't exist" set to sRGB are treated as sRGB instead of AdobeRGB.
Of course files that happen to be sRGB are then correct, because the fallback options matches. If set to "none", also "Interoperability Index: R98 - DCF basic file (sRGB)" are not correctly managed.

For example images you can download the attachments to this Firefox bug.
These should render the same, but don't. Only when I change the fallback option to point to a "Adobe RGB (1998).icm" profile I have on my PC they render the same.

[xnview]

Thanks to your detailed description I can reproduce the problem.

[xnview]

This problem is supposed to be fixed in XnView MP 1.5.0 beta. Please check and confirm the bug fix here.

[Propheticus]

Sorry to report that a side-by side comparison of 2 instances of 1.5.0 beta with "RGB profile used when embedded profile doesn't exist" set to 1) none vs 2) AdobeRGB ICM profile, still shows significant difference when viewing a photo that has no embedded profile, but does have Interoperability Index set to R03 - DCF option file (Adobe RGB)

Same can be see for sRGB interop images when using none vs sRGB fallback option.

[xnview]

right, related to the change when applying ICC profile. Will be fixed in b2

[Propheticus]

right, related to the change when applying ICC profile. Will be fixed in b2

Just saw and tested b2, looks fixed to me!