Problem summary:
Constant nodes with color set to (0,0,0,0) produce unexpected 'exr/dataWindow' metadata values when rendering EXRs
Customer reported version:
Nuke 13.2v7
Customer reported platform:
RHEL 9
Steps to reproduce:
1) Launch Nuke and create a Constant node in the Node Graph.
2) Select any format in the Constant's Properties, such as 1920x1080.
3) Create a Write node, and render an EXR file.
4) Create a Read node and load the rendered EXR file.
5) In the Read node's Properties, switch to the Metadata tab and search for "Window", observing how exr/dataWindow is equal to (1, 1, 1918, 1078):
Expected behavior:
When creating EXR files, the exr/dataWindow metadata values should match the original bounding box.
Actual behavior:
If an EXR file is created from a Constant node with color set to (0,0,0,0), the exr/dataWindow metadata value will be one pixel greater than expected for the X and Y, and two pixels smaller than expected for the Width and Height:
1920x1080 = (1, 1, 1918, 1078)
2048x1556 = (1, 1, 2046, 1554)
This occurs if the Constant's channels are RGB or RGBA, and whether or not the Write node is set to export RGB or RGBA.
Workaround:
Instead of using a Constant node, this particular issue does not occur when setting a CheckerBoard's colors to 0.
Reproduced by Support in:
Nuke 15.0v4 - Windows 10, macOS 13 Ventura
Nuke 14.1v1 - Windows 10
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Earliest version tested:
Nuke 12.0v1 - This issue appears to be in all tested versions of the product
