Skip to main content
S
simo.b
Inspiring
October 24, 2024
Answered

OCIO Duplicate Image to Profile ?

  • October 24, 2024
  • 1 reply
  • 293 views

Having an issue converting OCIO files from scene referred AcesCG to display referred ICC profiles in Photoshop 2025.  From reading the PS documentation I see that Edit > Duplicate to Image Profile command does this, as it offers all the available working ICC profiles as the target settings for the output.

 

If I set the output space to sRGB then then conversion matches fine, but if I select any other RGB profile as the target (such as Adobe RGB, ProPhoto etc) then the colours get too saturated ?  Looks like the command preserves the sRGB values but just display them as Adobe RGB/ProPhoto colours,  i.e. the same result as Assign Profile from sRGB > Adobe RGB etc in an ICC workflow. and the resulting saturation/hue shifts.

 

Any ideas why this is happening and If this is the correct behaviour and if so, why bother offering other output ICC output profiles and labelling it as a conversion if the gamut is always sRGB ? 

 

 

Correct answer cody_cuellar

Hi @simo.b,

The problem here is in OCIO, a config defines colorspaces with associated names, but to the application, it's just arbitrary names and colorspaces. Just because a display is called 'sRGB' in a config doesn't guarantee that it actually represents the sRGB standard, so the application has no way to know which ICC profile is appropriate. It would be extremely difficult and slow for us to iterate every installed profile trying to find one that closely represents a given arbitrary display space.

 

So unfortunately, right now the idea is the user is responsible for matching the ICC profile to a given OCIO target display space. For instance, if you render to a Display P3 display, you'd choose the appropriate Display P3 ICC profile in the other dropdown. We have raised an issue with OCIO that should be implemented in a future update that will allow OCIO to store metadata that we can use to smartly link the intended ICC profiles for a given display space. You can track the issue progress here https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1975

 

TLDR;

If the profile chosen doesn't match the actual OCIO display chosen, it's equivalent to doing 'assign profile' and assigning a different profile that doesn't represent the image encoding.

1 reply

C
Adobe Employee
cody_cuellarCorrect answer
Adobe Employee
August 14, 2025

Hi @simo.b,

The problem here is in OCIO, a config defines colorspaces with associated names, but to the application, it's just arbitrary names and colorspaces. Just because a display is called 'sRGB' in a config doesn't guarantee that it actually represents the sRGB standard, so the application has no way to know which ICC profile is appropriate. It would be extremely difficult and slow for us to iterate every installed profile trying to find one that closely represents a given arbitrary display space.

 

So unfortunately, right now the idea is the user is responsible for matching the ICC profile to a given OCIO target display space. For instance, if you render to a Display P3 display, you'd choose the appropriate Display P3 ICC profile in the other dropdown. We have raised an issue with OCIO that should be implemented in a future update that will allow OCIO to store metadata that we can use to smartly link the intended ICC profiles for a given display space. You can track the issue progress here https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1975

 

TLDR;

If the profile chosen doesn't match the actual OCIO display chosen, it's equivalent to doing 'assign profile' and assigning a different profile that doesn't represent the image encoding.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices