Sounds like you should contact support. It would be helpful if you could include a sample exr file to them (blanked if the footage is confidential) so we can see why this is happening.
Thanks,
Wouter
-- Sent from my HP Pre3
On 14 Nov 2011 22:47, Mike Owen <[email protected]> wrote:
BUMP!
Has anyone seen this behaviour in any version of Nuke? Any ideas what is causing it?
Thanks,
Mike
On 13 November 2011 12:11, Mike Owen <[email protected]> wrote:
Hi,
In Nuke v6.3v1, sometimes when creating a read node with an exr sequence, we get the actual read node label in the DAG going very strange and displaying random characters from the EXR filename to the extend that it is un-readable. Then as a result of bringing in this EXR sequence, ALL other nodes in the existing DAG which previously were fine, are now also corrupt in the same manner and just display random characters which generally seem to be made up of the original node label name.
Has anyone seen anything like this before? Is it a known bug in this version?
Thanks,
Mike
_______________________________________________ Nuke-users mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-users
