# Adobe RGB 1998 Output in OCIO config

Dear community,

I’ve decided to write here because I didn’t find a solution on the net to this kind of problem.
I’m a 3D artist as well as a photographer, I worked for years with the standard photographic process (lightroom, C1, Photoshop) to develop real photographs using Adobe RGB wide gamut for print.
Since the improvement of OCIO config in render engines, I started working with ACEScg color space and take advantage of the wider color space but I was wondering why Adobe RGB and Prophoto are not included in the view transform list.
Since that sRGB, rec 709, and rec 2020 are included, is teorycally possible to also develop custom view transform like Adobe RGB and Prophoto?
If yes where can I start to study to figure out the way?

Thanks a lot to all

I recall seeing AdobeRGB being implemented in the OCIO config of Redshift or C4D. You may pull it from there if you can access it. ProPhotoRGB as a view transform doesn’t make a whole lot of sense because there isn’t a display that reaches this.

You’ll need to know your way around editing OCIO config files a bit to make it work but hope this gives you some direction to start in.

1 Like

Hello @alessandroconsonni,

When the OCIO Configs VWG reviewed the previous config and its usage, we did it with the intent of drastically reduce the number of colourspaces and LUTs shipped. Here is the spreadsheet that reflect those decisions: OpenColorIO-Config-ACES "CG and Studio" Transforms - v1.0.0 - Google Sheets

This does not mean that we will not add them back in the future. Feel free to create an issue on the repo where it is going to have more visibility: Issues · AcademySoftwareFoundation/OpenColorIO-Config-ACES · GitHub

Cheers,

Thomas

1 Like

Thanks

On Windows the config is located here:
C:\ProgramData\Redshift\Data\OCIO

I would assume a similar location on mac, wherever Redshift itself is installed.

Sharing it from my Dropbox as well:

I had a look at how they implemented it.
I’m not really sure how they got to their data because the values are different from when I check the matrix to go from AP0 to AdobeRGB through this site.
I also thought AdobeRGB gamma is 2.2 but theirs is slightly lower. Not exactly sure why.

  - !<ColorSpace>
family:
description: |
isdata: false
categories: [ file-io ]
encoding: sdr-video
from_display_reference: !<GroupTransform>
children:
- !<MatrixTransform> {matrix: [ 2.041587903811, -0.565006974279, -0.344731350778, 0, -0.969243636281, 1.875967501508, 0.041555057407, 0, 0.013444280632, -0.118362392231, 1.015174994391, 0, 0, 0, 0, 1 ]}
- !<ExponentTransform> {value: 2.19921875, direction: inverse}
- !<RangeTransform> {min_in_value: 0., min_out_value: 0., max_in_value: 1., max_out_value: 1.}



I’d say use at your own discretion and do plenty of tests .

Thanks! I’m not sure on how to add it to my usual ocio config but before to bother you I’ll do some research and try. Thanks a lot for your help!

If you check the Adobe 1998 spec, you will see that the exponent is in fact 2\frac{51}{256}=2.19921875, not 2.2.

The matrix given is the XYZ D65 to Adobe 1998 matrix, as XYZ D65, not AP0, is the display reference space. The spec gives the matrix to five decimal places, but I assume the version there is calculated from the primaries to a higher precision.

Edit: corrected the denominator in the fraction to 256 instead of 255, because I copied it wrong!

1 Like

Thanks for the explanation! Totally makes sense now.

Looks like the colourspace uses from_display_reference, so the values are from CIE-XYZ-D65 to AdobeRGB and appear to be correct. AdobeRGB defines its transfer function as 2 + 51/256 = 2.19921875 how those numbers were derived, couldn’t tell you. Either way, useful to now have links, thanks Shebbe.

As a nonprofessional in color science, I tried to find out a “handcrafted” way to implement Adobe RGB output without luck. I know it’s pretty annoying but can someone suggest to me at least a software to use to rewrite OCIO code? with text edit it’s incredibly difficult to do.