ID 246654 - Copying Quicktime timecode metadata can produce incorrect results in the CopyMetaData node

Follow

Problem summary
Copying Quicktime timecode metadata can produce incorrect results when using a dropframe timecode

Customer reported version
nuke.10.0v4

Customer reported platform
centos6

Steps to reproduce

1) Open Nuke

2) Read in the attached file

3) Create a CheckerBoard node and attach it to the image input of a CopyMetaData node

4) Attach the Read node to the Meta input of the CopyMetaData node

5) Attach to a Write node, and render out a .mov file in Apple ProRes 4444 codec with 59.94 fps and write time code enabled. 

6) Read in the newly Written file, the compare the metadata, the input/timecode will be incorrect, as shown below:



Reproduced by support
This problem has been reproduced on:
Nuke 10.0v5 - CentOS 6.8 - Windows 10 - MacOSX 10.12
Nuke 10.0v1 - CentOS 6.8
Nuke 9.0v9 - CentOS 6.8
Nuke 9.0v1 - CentOS 6.8 - Windows 10 - MacOSX 10.12

Expected behaviour
For the timecode exported to be correct

Actual behaviour
It wasn't
 

    We're sorry to hear that

    Please tell us why