profile created with the rawtherapee tool
RTv2_ACES-AP0_g1.000000_s0.00000.icc (928 Bytes)
this is the RT version ( neutral profile ) converted to srgb
rt-resolve-aces.zip (17.1 MB)
The rt-aces.tif in the .zip is the rt output with linear gamma and AP0
primaries 
Edit
RT with dcp converted to srgb
This image has ap0 primaries and rec.709 trc, it isn’t linear.
Is this that you want?
I think that the V2 e V4 icc AP0 profiles in rawtherapee have srgb trc…
The custom icc profile i’ve attached before has linear gamma.
your tiff with the correct icc profile assigned (RTv2_ACES-AP0_BT709_g=2.2_s=4.5.icc|attachment (24.9 KB) )and converted to srgb
Some confusion in our discussion.
1 We aren’t the best people to ask about workflow. acescentral.com would be a better place to ask what would be the ideal file specs to ingest without an IDT.
2 Only ACES2065-1 and ACEScg can have AP0 primaries. The rest are AP1. ACEScct has its own encoding (not Rec709) and is ACEScc with a toe. This is by memory. Please refer to
for the exact information.
If this forum is not the best place to ask how to work with RT…, where should that place be?
Well, my best guess is that this is fundamentally incorrect.
If we read:
and many others, including the technical documentation, it is clear that all those ACESxxx color spaces are part of a framework mostly oriented to movies, but yet usable with still frames.
But all of this is mostly an out of topic discussion regarding the question asked.
I think the OP is more than capable to create his own workflow with all that conversions between different color spaces (all of them part of the ACES specification). All that has been asked is how to get a proper starting image that meets his input needs. And how to do it with RT.
I guess that answer has already been answered. All we have to do is wait for him to test it and report back if the proposed solution gives him what he needs
The storage file should have always AP0 primaries (tiff or exr).
Probably he just needs to decode the raw file with the dcp tone curve enabled (like resolve does) and export a linear tiff with AP0 primaries.
And by the way, this is a comparison of both ACESp0 and ACESp1 (done with DisplayCal):
(ACEScg has the same gamut as ACESp1)
Please be patient with me and reread my posts. I believe they are relevant and informative. We have already established how to do colour management in RT. Besides my discussion on color space, processing, etc., the rest is totally about profiles and ACES. Where better to learn than from ACES Central and the technical PDFs?
@Elle has been mentioned multiple times. She can be reached via various mailing lists and email:
Other people to ask are @KelSolaar and Troy Sobotka. Elle and Troy no longer frequent this forum for various reasons. This wraps up my involvement in this thread. Hope you found it helpful.
Sorry Afre I don’t see how your posts are relevant to this discussion.
If you want to be helpfull to the discussion you should have downloaded that picture and see that he doesn’t have create an icc profile but rather used the pre-installed one in rt
This is why i have directly linked the AP0 linear profile.
The second question is how to match the resolve raw decoding, does resolve use the dcp tone curve? how to do the same in rawtherapee?
Here ilias_giarimis has kindly provided the dcp profile and with the dcp enabled rawtherapee and resolve are a very close match.
I don’t understand why you suggest him to contact elle, troy or goes ask in the aces central forum.
Hi everyboby,
i did import into RAWtherapee GUI the DCP file, ICC files, i did setup my output profile, and after a while, it’s works fine with RESOLVE !
The good result from RT: ACES AP0 Lin
I have another question:
What i’m missing with the CLI version ?
Thanks !
JC
Here is a small version of the good TIF ACES APO from the Rawtherapee-GUI:
kl-fp-goodAP0_small.tif (2.4 MB)
Here is a small version of the wrong version with the previous PP3 file and Rawtherapee-cli:
kl-fp-cli-bad_small.tif (2.4 MB)
rawtherapee-cli -o kl-fp-cli-jeudi.tif -p aces2.pp3 -t -c kl-fp.dng
The “bad” render is of gamma-transformed data with no embedded profile, and the “good” render is of linear data with the linear ACES AP0 profile embedded. When I view both with their respective color management “needs”, I don’t see an appreciable color difference.
Don’t know enough about RT-cli to speak to why it may behave differently at export, so I’ll leave that to the devs.
Hmm… That is interesting, because it hints that the other software was doing something it should not have been.
Applying a nonlinear tone curve this early in the pipeline shouldn’t be done, under the assumption that the tools later on in the processing pipeline are expecting linear input. Which if the goal is ACES P0 linear, indicates the later tools are expecting scene-linear data.
IIRC, all of the built-in/bundled output profiles in RT use an sRGB TRC.
To output linear data, you need to use the ICC profile creator and save the file where RT will recognize it as an output profile.
Well, that is a part of the reason that I spent time writing the posts and providing references for further reading. Even though they might be considered off topic, I think they would be informative to those visiting this thread. (That said, 2-3 hours of sleep per night doesn’t give me the best judgement. 
)
@Jean-Charles_Fouche I am glad that the GUI is working for you. I know you are still looking to resolve the CLI issue but note that you could copy and apply the settings and export the files within the GUI’s file browser. That might be handy in the meantime.
Something i’m not understanding:
Not all photo viewers are color managed
Not all image viewers are colour managed. What is your colour management setup?
Edit: @paperdigits beat me to the reply! 
Yes the DCP tone curve it’s not compatible with aces and it should not be used but this isn’t a true aces workflow either
Windows photo viewer is color managed
Many Thanks !
JC
