Hi, I don't know if this is a bug, but I'm having an issue with the autocrop function when selecting exr as an output in the write node... or I simply don't understand the expected behavior of this option.
I was expecting it would ignore all pixel information outside the given resolution and render a non-overscan (no extra information) image. But I can't seem to make it work. When I import my rendered sequence back in Nuke, it still seems to contain extra data in it. Another proof that it does keep the extra info is it will fail to import that sequence in Flame (Flame doesn't support overscanned exr's AFAIK). My workaround is to put a crop before the write node, but I would really like that to work. Any ideas? I'm I doing something wrong or is the function just broken? Cheers
<<attachment: autocrop_nuke.png>>
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
