What's new in app.color.io
Learn what's new in the latest version of Color.io. Share your ideas and report any issues here.
Changelog
Learn what's new in the latest version of Color.io. Share your ideas and report any issues here.
Feedback
Learn what's new in the latest version of Color.io. Share your ideas and report any issues here.
Merged in a post:
@jakob If I understand correctly you want a workflow similar to this:
To enable this workflow, we would bypass all ACES color management in Color.io, both the IDT and the ODT. Is this what you want? Are there any use cases where you'd want only the IDT or only the ODT disabled but not both? Thanks!
@monokee
Yes this is exactly what is needed for an aces workflow. I would always need both the IDT and the ODT disabled. I would suggest making it possible to have all the flavours of aces available as aces cct is primarily used for color and other flavours of aces such as aces cg is used for vfx previews and compositing.
@jakob I just published an update that allows you to set the working color space in the Export Panel:
Things to note when you override the default:
@monokee
Thank you. This is great.
Just tried an aces cct lut and it works as expected. The dctl version gives me errors and does nothing. Would it be possible to choose to add the custom part of your IDT to the aces cct lut? I am getting very different images when going from logC to rec709 with your idt and odt compared to adding my own idt and odt in ACES 1.3 an then using the aces lut. I have attache two screenshots. You could also make it possible to download your custom idt as a lut together with the ACES cct lut. With ACES 2.0 around the corner it probably makes sense to add the creative part of your IDT into the look as this will make switching aces versions a lot smoother.
@jakob Sure we could bake the gamma modifier directly into the ACES LUT. The only problem with that is that the gamma modifier is IDT specific. So when you bypass the IDT/ODT for export, you would still need to keep some reference to the intended IDT in order to get the correct gamma modifier which already sounds like a convoluted mess from a UX standpoint.. I'm starting to think that it would be better to move all of this logic to the next version of the DCTL generator which would allow us to make things more explicit by including basic UI controls for Resolve as well as doing more things algorithmically vs using LUTs. We would include a toggle for the gamma modifier in the DCTL so you can turn it on or off yourself.
Actually, as per the previous conversion I had with Rune via Email, a lot of this sounds like a work-around for the current lack of more advanced DCTLs you really need for your workflow.
I think it would be better to focus on beefing up the DCTL generator than hacking more color management options into the LUTs. Would you agree?
Yes I agree. It will be a more elegant solution to handle it all in the DCTL while also giving us basic ui controls which would be a big step forward.
Thinking about the ACES lut workflow again I think there is a solution. I think the custom part of your aces IDT the custom gamma modifier part of the IDT should be part of the aces lut export by default as it is a part of the look and not a part of the aces color management system. My main worry about only being able to get correct colors via the dctl in resolve is that I will not be able to easily share the show lut with vfx or other color grading system like baselight which we also use.
I am still really excited about the DCTL development and I think it will be a unique solution in the market.
@jakob You're right. It actually wasn't hard or complicated to do this either, it was just my brain. I just published an update that automates this: When you export to any ACES color space, the IDT specific gamma modifier of your current preview in Color.io is baked into the ACES LUT so you should get the exact same image everywhere.
Thats great. I will test it right away.
Is there a way to see what build I have loaded in my browser? What should the build be for it to have the new functionality available?
@jakob There's no build version, whenever you reload the page you're served the latest update. Do you have ACES 1.3 reference gamut compression enabled in your IDT? Gamut compression must be enabled or the results won't match with the Color.io preview. Also make sure Halation is disabled in Color.io when comparing.