ID 560512 - Timecode metadata is not preserved and always defaults to 00:00:00:00 when writing MXF files

Problem summary:
Timecode metadata is not preserved and always defaults to 00:00:00:00 when writing MXF files
 
Customer reported version:
Nuke 14.1v2
 
Customer reported platform:
Windows 11
 
Steps to reproduce:
1) Launch Nuke and create a CheckerBoard node in the Node Graph.
2) Create an AddTimeCode node.
3) Create a Write node, and export an MXF file.
4) Use a Read node to load the MXF file, and observe how the timecode metadata is 00:00:00:00 instead of 01:00:00:00

 
Expected behavior:
MXF files generated by Write nodes should preserve the timecode metadata of any upstream nodes. 
 
Actual behavior:
When Writing MXF files from Nuke, the timecode metadata is always set to 00:00:00:00
 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Nuke 15.0v2 - Windows 10, macOS 13 Ventura
Nuke 15.0v1 - Windows 10
Nuke 14.1v2 - Windows 10
Nuke 14.1v1 - Windows 10 - Regression
 
Unable to reproduce bug in:
Nuke 14.0v6 - Windows 10
 
Earliest version tested:
Nuke 14.0v6 - This issue doesn't appear in this version and has regressed