Thats what i do - reading in sRGB sequence as linear plonk down a standard colorspace node setting input to sRGB output to Linear
do any comp work / grading put down a final colorspace node setting input to Linear - output to sRGB set the display LUT to RAW(sRGB) - (or use a OCIO display node with input color space set to srgb8, display device sRGB and view transform Raw. Neil Scholes +44(0) 7977 456 197 www.uvfilms.co.uk On 31 Aug 2012, at 13:47, Schneider, Abraham wrote: > And an additional question: > > is there a way to go from the old style Nuke linear colorspace to the ACES > colorspace? Both linear of course, but at least the RGB chromaticities are > different, whitepoint as well? > > Of course, it would only be possible to go from Nuke linear to ACES without a > loss, not the other way around because of the different gammut. > > Thanks, Abraham > > > > Am 31.08.2012 um 11:13 schrieb Schneider, Abraham: > >> Hi there! >> >> I just played around with the OCIO nodes/modes in Nuke 6.3v8. I also had a >> look at the ACES workflow/config from the opencolorIO.org website. I've >> added this 'aces' config to Nuke by adding the config.ocio as the custom >> config. >> >> Seems to work fine so far. But there is one thing in this whole setup/config >> that I doesn't really get: how do I use sRGB/rec709/video footage (stills >> and/or movies) in a ACES environment? Normally I'd assume to switch the Read >> node to raw and/or linear (because the Read doesn't support OCIO yet), add a >> OCIOColorSpace, set IN to something like sRGB/rec709/etc. and the OUT to >> aces, to convert the image to the ACES colorspace. But there is no IN >> setting for sRGB/rech709/etc.! I can convert ARRI logC, analog film scans >> (cineon coded), sLog, etc., but not 'video' or other display referred >> encoded material (neither in the iff config coming by default with Nuke nor >> in the aces config from opencolorio.org). So how am I supposed to use still >> images, video stock footage, etc. in an ACES workflow in Nuke? >> >> Only way I tried it at the moment was to switch the Read to "sRGB" (or >> rec709 or gamma 2.2 etc.), add a normal Colorspace after the read that >> converts from linear to AlexaV3LogC and add a OCIOColorSpace with IN = >> 'logc' and OUT = 'aces'. Seems to work, but doesn't seem to be a clever way. >> >> Do I miss something or is this just not supported at the moment in this ACES >> config/workflow? Using the 'spi-vfx' config in comparison, there is the >> option to set the IN to 'vd8' or 'vd10' or something like that. But >> 'spi-vfx' is not using the ACES colorspace, right? >> >> Abraham >> >> >> Abraham Schneider >> Head of VFX pipeline / VFX Supervisor >> >> >> ARRI Film & TV Services GmbH >> Tuerkenstr. 89 >> D-80799 Muenchen / Germany >> >> Phone +49 89 3809-1269 >> >> EMail [email protected] >> www.arri.de/filmtv >> ________________________________ >> >> >> ARRI Film & TV Services GmbH >> Sitz: München Registergericht: Amtsgericht München >> Handelsregisternummer: HRB 69396 >> Geschäftsführer: Franz Kraus, Dr. Martin Prillmann, Josef Reidinger >> _______________________________________________ >> Nuke-users mailing list >> [email protected], http://forums.thefoundry.co.uk/ >> http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > > _______________________________________________ > Nuke-users mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users > _______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
