Problem summary Combining multi-part exr metadata causes the result to become corrupted. Customer reported version nuke.10.5v5
Customer reported platform centos7
Steps to reproduce
1) Launch Nuke and open the attached script.
2) Using the first write node, render out a test exr following the pre-determined outputs. Then read the render into the write node that follows it.
3) After rendering the second write node, the Singlepart.exr render will fail and produce a variation of the following errors:
ERROR: Read1: Error reading pixel data from image file "/Users/foundry/Documents/multipart.exr". Unexpected data block y coordinate. ERROR: Read2: Error reading pixel data from image file "/Users/foundry/Documents/multipart.exr". Error reading pixel data from image file "/Users/foundry/Documents/multipart.exr". Scan line 43 is missing.
Workaround
- Removing `exr/chunkCount` from the metadata of the Singlepart.exr. - Choosing `default metadata` in the write node of Singlepart.exr. - Adding the original displayWindow (bounding box) before the write node of Singlepart.exr. - Changing the output channels to `all` in the write of Singlepart.exr (writing multi-part EXR again). - Writing the Singlepart.exr with ZIP compression. - Writing the Singlepart.exr with interleave set to "channels and layers" or "channels, layers and values".
Reproduced by support Nuke11.0v3- MacOS 10.13 - Windows 10 - Linux Centos 7.4 Nuke11.0v1- MacOS 10.13 - Windows 10 - Linux Centos 7.4 Nuke10.5v6- MacOS 10.13 - Windows 10 - Linux Centos 7.4 Nuke10.5v1- MacOS 10.13 - Windows 10 - Linux Centos 7.4 Nuke10.0v6- MacOS 10.13 - Windows 10 - Linux Centos 7.4 Nuke10.0v1- MacOS 10.13 - Windows 10 - Linux Centos 7.4 Nuke9.0v9- MacOS 10.13 - Windows 10 - Linux Centos 7.4 Nuke9.0v1- MacOS 10.13 - Windows 10 - Linux Centos 7.4 Nuke8.0v6- MacOS 10.13 - Windows 10 - Linux Centos 7.4 Nuke8.0v1- MacOS 10.13 - Windows 10 - Linux Centos 7.4 Nuke7.0v10- MacOS 10.13 - Windows 10 - Linux Centos 7.4
Earliest version tested Nuke 7.0v10
Expected behaviour Nuke would be able to render the multipart exr without any issues.
Actual behaviour The written exr corrupts and is unreadible.