How fantastically interesting! I suppose this explains why there is no B44A option for compression type in Nuke as well since this was added more recently as well.
I for one would be very interested in having access to the most recent OpenEXR library working properly in Nuke. I sent an email explaining the situation and what has been discussed here to [email protected], so hopefully that should further the hopes of this getting fixed. On Sun, Mar 11, 2012 at 4:36 PM, fnordware < [email protected]> wrote: > ** > *Jed Smith wrote:* > It seems like Nuke does not handle chroma subsampled EXR files properly? > Is this a bug? Has anyone else experienced this problem? > > > It looks like Nuke is actually using an outdated version of the OpenEXR > library. Nuke, of all programs! > > The 4:2:0 Luminance/Chroma sampling was added to OpenEXR after the initial > release. The library now provides a class that will handle the conversion > to and from 4:4:4 RGB, but you have to be using a version of the library > that supports it and be on the lookout for that situation. > > Something else I recently noticed: Nuke can't handle EXR files if they > have channel names longer than 32 characters (at least the Mac version). > This is another sign they're using the old library. OpenEXR originally had > that limit, but it was expanded to 256 characters in 2007 with OpenEXR 1.6. > Older versions of the library will reject these files. > > But the Luminance/Chroma stuff was added in 2004 with OpenEXR 1.2! > > > Brendan > > _______________________________________________ > 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
