via Aces CCT from Nuke to Davinci colorshifts

Hey,

I do have a short, which was comped in nuke, all cgi basically, we used the rec709 ODT all the time and also baked that into the mp4s we had for online reviews…
Now I thought, Davinci and exrs I am not so sure how that works and I had problems loading up the different shots as we had 4-6 padding per shots, which is a different story… anyway I then thought why not use Aces CCT to get all over via prores 10 bit as all is in the right ballpark anyway…

Did that but I am having colorshifts now when viewing the Aces CCT prores files through rec709 odt compared to the stuff I see in nuke and what we used as lutted footage.
Especially yellows are more saturated…

I never have used AcesCCT before, but I thought it was made for my usecase, get with some fidelity through a “non float capable fileformat” into another application and still have some room in the images…

My last resort to have the same baseline is now to use lutted prores with the baked ODT… but I dont understand why the colors are off in the first place, it is not much but they are off…

Anyway one other thing I could do ofcourse is give the exrs a second chance and get my paddings in line so they all end up being the same…

BTW I went through OTIO and then replaced the media ref via python to the exr image sequences and then went back, might also be that the problem is buried somehwere there…

Looking forward to suggestions.
Nuke into davinci …

Cheers
Johannes

PS nerd question
when I am having an exr image sequence in davinci, and I create a proxy from the exr image sequence… how the heck is this supposed to be working ? having a half float format and then proxies are always int … has anybody any experience with this ?

Hey…
it seems like I fell for the gamma/colorshift in Quicktime on Macos, which I used as a ref for color accuracy.
On windows all is fine (Resolve is the same as in OpenRv as in the MediaPlayer with a lutted mp4). Using OpenRv on Macos for the mp4 as a reference and then using Aces Cct in Resolve also yields the same result, only Apple Quicktime is off…
I have not fully gained an overview, but it seems I could tag my mp4s differently so they end up being more the same cross plattform and browsers, but it is not a Resolve or Aces issue but Quicktime on macos. Such a pitty that in 2024 this still is an issue.