Color management

[Armas]

There is a bug in color profile management
(JPEG/Tiff write option: maintain ICC profile):
Correct profile embedding only in connection with batch processing.
Normal "Save" and "Save as" however embed the user-defined monitor profile or no profile at all.

[xnview]

could you explain the problem?

[Armas]

Bonjour Pierre,

i hope, i can explain it with some screenshots (german user interface):

1. XnViewMP color profile settings

2. You have a photo with embedded color profile (sRGB IEC61966-2.1)
3. jpg write settings: maintain ICC profile

4. As "save-as" result you have a photo with embedded user defined monitor profile (Acer...), that's not correct

3_cp_save-as.jpg (48.95 KiB) Viewed 2063 times

5. The same photo in batch process, option: apply color profile

6. Result is the correctly embedded original color profile

5_cp_batch.jpg (53.31 KiB) Viewed 2063 times

Salutations à la France,
Arno

[xnview]

yes, when opening a photo the color profile is always converted (if setting on), so when you save, the new color profile is used.

[Armas]

Thanks for the answer, but I don't know if you understood me correctly.
I think the setting "General - Colour profile" concerns the user's monitor profile (For Display...), or am I wrong?
However, the monitor colour profile should never be embedded in a photo. Otherwise the display on another monitor would be wrong.
And why the saving is correct in batch mode (original profile) and different in normal saving (monitor profile).
Maybe you can explain this.

I became aware of the problem through the page http://fotovideotec.de/cms_tauglichkeit/

Arno

[AlonLevitan]

I know my reply is quite late, but I wanted to say that it seems like there's a bug specifically with the "Maintain ICC profile" option when using JPEG/TIFF write, but it works correctly during batch processing. However, when using the normal "Save" or "Save as" options, it embeds the user-defined monitor profile or sometimes no profile at all. It's definitely a bit frustrating, but hopefully, the developers can address this in a future update.