Re: ACES 1.0 release - question on ODTs
Haarm-Pieter Duiker <[email protected]>
| Newsgroups | gmane.comp.video.openexr.devel |
|---|---|
| Message-ID | <CAO0BOOTzhHBooCWAd5vbOJjdPCzp2xGoBvvBCwL=D2wUn2RjVg@mail.gmail.com> |
Thanks for the clarification. Yes, the ACES variable names and color spaces should take precedence if you are adding support for ACES. HP On Fri, Jan 16, 2015 at 8:01 AM, Gonzalo Garramuno <[email protected]> wrote: > On 15/01/15 22:48, Haarm-Pieter Duiker wrote: > >> s a readme that has the matrices to go from the ACES AP0 and AP1 >> primaries to XYZ here >> https://github.com/ampas/aces-dev/blob/v1.0/transforms/ctl/ >> README-MATRIX.md >> > > Sorry for not being clear. Currently the openexr_ctl 1.0.1 demos come > with two .ctl files which were templates before a standard was set. The > first one, transform_RRT.ctl is a rendering transform (RT), works in RGB > and provides output in XYZ. The other transform, transform_display_video > is an output device transform (ODT), works by taking those XYZ values and > returning R,G,B display values. > It seems those transforms are now replaced by the transform in ACES. > However the ACES transforms work in all cases as input in RGB and output in > RGB. They also use other variable names. > Am I right in assuming I should conform my C++ code to follow the ACES > variable names and standard? > > _______________________________________________ Openexr-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/openexr-devel