ID 595366 - The input/timecode metadata becomes missing when adding an AddTimeCode node with fps knob value greater than 30 when rendering an EXR file format.

Problem summary
The input/timecode metadata becomes missing when adding an AddTimeCode node with fps knob value greater than 30 when rendering an EXR file format.
 
Customer reported version
Nuke 15.1v3
 
Customer reported platform
Windows 10
 
Steps to reproduce
1) In Nuke, create a Checkerboard node.
2) Create an AddTimeCode node and in the Properties bin, disable the get FPS from metadata knob. 
3) Set the fps knob value above 30.
4) In the Node Graph, add a Write node, then set the filepath for an EXR sequence.
5) Render the Write node and read-in the newly created EXR sequence.
6) View the Metadata tab of the Read node.
6) Playback the frames of the Read node, observing the metadata for input/timecode.
 

 
Expected behavior
The input/timecode metadata should remain on the rendered frames.
 
Actual behavior
The input/timecode metadata will be removed from the rendered Read node for however many frames were set in the fps knob of the AddTimeCode node beyond 30 frames. So if you set the fps knob to a value of 45, there will be up to 15 frames where the input/timecode metadata is missing from the Read node.
 
This issue did not occur with other frame sequence formats such as DPX, PNG, JPG, TIF, MXF etc.
 
Workaround
There is no available workaround at this time.
 
Reproduced by Support in:
Nuke 15.1v5 - Windows 11, macOS 13 Ventura
Nuke 14.0v1 - Windows 11, macOS 13 Ventura - regression
 
Unable to reproduce bug in:
Nuke 13.2v9 - Windows 11, macOS 13 Ventura
 
Earliest version tested
Nuke 13.2v9 - This issue doesn't appear in this version and has regressed