Problem Summary:
When reading Deep EXR files, Nuke ignores the pixel aspect information in the file header so that images are always read in with pixel aspect ratio of 1.
Additionally when Nuke writes out Deep EXR files it ignores the pixel aspect ratio of the working format and writes them out with pixel aspect of 1.
Customer Reported Version:
Nuke 10.0v5
Customer Reported Platform:
Linux CentOS6.9
Steps to reproduce:
1) Open Nuke
2) Create a 'DeepRead' node, import in Deep EXR file with a Pixel Aspect of 2
3) Create a 'read' node, import Normal EXR file with a Pixel Aspect of 2
Result: The 'DeepRead' node will display with a pixel aspect of 1
Additional Steps for Writing Deep pixels:
1) Write out a DeepImage with Pixel Aspect Ratio of 2
2) Read it back in and use a ViewMetadata
3) Result: The Pixel Aspect Ratio is 1
Workaround:
Add a 'DeepFormat' node to the 'DeepRead' node and format the node to have a pixel aspect of 1
Reproduced by Support in:
Nuke 13.1v1 - Windows 10, macOS 10.15
Nuke 13.0v1 - Windows 10
Nuke 10.5v5 - Windows 7
Nuke 10.5v1 - Windows 7
Nuke 10.0v5 - Windows 7
Nuke 10.0v1 - Windows 7
Nuke 9.0v9 - Windows 7
Nuke 9.0v1 - Windows 7
Nuke 8.0v7 - Windows 7
Nuke 8.0v1 - Windows 7
Nuke 7.0v1 - Windows 7 - Mac 10.12 (Sierra) - CentOS6.9
Expected Behavior
When a Deep EXR is read through the 'DeepRead' node, its pixel aspect should be as the EXR defines it as.
Actual Behavior
When a Deep EXR is read through a 'DeepRead' node, its pixel aspect is defaulted to 1