1. Messages
  2. ACES OCIO configs, testing and feedback

Re: ACES OCIO configs, testing and feedback

Matt Plec <mp...@...>
 

I'm a bit late to the party, but for what it's worth, Red log (with their various red color primaries I assume?), Canon log, and GoPro "protune" were popular requests for inclusion in the default Nuke set, so I expect people will also want to convert between those and ACES.

Two others worthy of consideration are ProPhoto and Adobe RGB. May sound crazy but hear me out.... Having them available makes it possible to produce stills out of vfx tools in a form print/marketing can work with directly and also to bring in stills from print/photography workflows directly to an ACES reference space comp/render.

Cheers,
Matt


On Fri, Nov 7, 2014 at 7:02 PM, Haarm-Pieter Duiker <li...@...> wrote:
On the IDT side, the current Academy repo includes IDTs for the following cameras / configurations
  • Arri Alexa with the following exposure indices: EI800, EI640, EI500, EI400, EI3200, EI320, EI2560, EI250, EI2000, EI200, EI1600, EI160, EI1280, EI1000
  • Sony F65 Tungsten and Daylight
  • Sony F35
Are those very specific IDTs what you're looking for? What other camera / IDT color spaces would be helpful? Red? Canon? GoPro?

On the point about including conversion between different primaries, what primaries sets would be useful? Rec2020? Rec709? P3? Arri wide gamut?

We're also looking into the legal vs. full range options for spaces like ACESproxy.

Thanks for the suggestions so far,
HP




 



On Thu, Nov 6, 2014 at 7:50 AM, Francois Lord <franco...@...> wrote:
Yes, and I suspect we will continue to receive camera native material for a while. VFX houses will adopt ACES more quickly than production houses.

Would it be a good idea to include profiles for Rec.2020 so that we can easily convert CG renderings to and from ACES when working with the ocio config?


On Wed Nov 05 2014 at 4:53:54 PM Steve Agland <sag...@...> wrote:
On 6 November 2014 06:56, Haarm-Pieter Duiker <li...@...> wrote:

Could you provide some example of when and how you would use the IDTs with OCIO? From a number of other sources, we're hearing that most IDTs will be applied by the Camera SDKs / toolsets so most OCIO-supporting applications will interact with ACES, ACESproxy or ACESlog images rather than images in the camera raw color spaces.

It's not uncommon to receive external material in camera color spaces and to want to ingest them using the same OCIO-supporting tools that are used for color management internally. That could be scripts, command-line utilities or apps like Nuke. Having the IDTs in OCIO just makes that easier, even though the rest of the pipeline won't necessarily use those transforms.

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@....
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@....
For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "OpenColorIO Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ocio-dev+u...@....
For more options, visit https://groups.google.com/d/optout.
Join ocio-dev@lists.aswf.io to automatically receive all group messages.