When applying certain operations to EXR files like Reformat, Transform or Motion Blur, the frames before and after the clip frame range hold the image rather than appearing black, even though they were set to ‘black’ in the Read node.
This only seems to happen to EXR files with certain compression types. It was reproduced with ZIP, PXR24 and PIZ compressed files, but not with ZIPS or RLE.
Customer reported version
Nuke 10.0v4
Customer reported platform
Windows 10
Steps to reproduce
Read in a ZIP compressed EXR file. Some examples from netqa are attached.
Add either
- a Reformat node
- a Transform node and change the scale to something other than 1
- a Motion Blur node
In the Read node > Frame range, change in the 'after' dropdown 'hold' to 'black'
Select 1 frame after the final frame in the sequence (i.e. if last frame is 100, view 101 in the timeline)
Switch views between the Read node and the Reformat node. Result: Read node displays black, Reformat node displays held image
Workaround
Add a Retime node after the Read node and set before and after frame range to ‘black’.
Reproduced by support
8.0v1+7, 9.0v1+8, 10.0v1+4 Windows 7
Doesn’t happen in 7.0v10
Expected behaviour
Settings from the Read node's before and after frame range values should carry through the following nodes.
Actual behaviour
When the before and after frame range value is set to black, this setting don't always carry through the following nodes.