Problem summary When importing EXR sequences into Nuke Studio, if these EXR sequences contain Cryptomatte metadata from the 3D renderer, this can cause Nuke Studio to create large project files.
These large project files can lead to longer load/save time as well as other performance based issues, and due to the nature of versioning within Nuke Studio each version contain this metadata will continue to grow the project size exponentially.
Customer reported version nuke.12.0v3
Customer reported platform centos7
Steps to reproduce
1) Import the attached 'example1_v001.exr' file (no Cryptomatte metadata) into Nuke Studio
2) Save the Nuke Studio project and view the file size Result: expected size
3) Import the attached 'example2_v001.exr' file (contains Cryptomatte metadata) into the same Nuke Studio project
4) Save the Nuke Studio project and view the file size Result: project size significantly larger
5) Duplicate the 'example2_v001.exr' file, renaming it to 'example2_v002.exr'
6) Import the attached 'example2_v002.exr' file into Nuke Studio Result: project size doubles from before
Expected behaviour Cryptomatte metadata that is embedded into EXR files, should not increase the project size this significantly
Actual behaviour Cryptomatte metadata that is embedded into EXR files, increases the project size significantly, causing longer loading and saving times.
Workaround We suggest to remove the Cryptomatte metadata before rendering to Nuke Studio.
If compositing through Nuke, we would recommend removing this metadata using a ModifyMetaData node. This can be done by setting the 'remove' attribute to the associated metadata 'key' and 'value' information before the Write node.
Reproduced by support This bug has been reproduced in: Nuke Studio 12.0v3 - Windows 10 - CentOS 7 - MacOS 10.14.6 Nuke Studio 11.3v1 - Windows 10 Nuke Studio 11.2v1 - Windows 10 Nuke Studio 11.1v1 - Windows 10 Nuke Studio 11.0v1 - Windows 10 Nuke Studio 10.5v1 - Windows 10 Nuke Studio 10.0v1 - Windows 10 - CentOS 7 - MacOS 10.14.6
Unable to reproduce bug in: Nuke Studio 9.0v1 - Windows 10 - CentOS 7 - MacOS 10.14.6 (exr compression type not readable)
Earliest version tested Nuke Studio 10.0v1 - This issue appears to be in all versions of the product
