Problem summary When importing media into a Nuke Studio or Hiero timeline, the timecode for the clip is derived from the 'input/timecode' metadata
It has been discovered that if an image sequence contains an original timecode that is not numerically sequential, when imported it will be imported as sequential from the start of the clips timecode
An example of a non-sequential timecode would be: Frame 1 = 00:10:01 Frame 2 = 00:10:03 Frame 3 = 00:10:05
An example of a sequential timecode would be: Frame 1 = 00:10:01 Frame 2 = 00:10:02 Frame 3 = 00:10:03
Note: Testing this within Nuke shows the correct result derived directly from the input timecode metadata.
Customer reported version hiero.11.3v5
Customer reported platform centos7
Steps to reproduce
1) Within a new Hiero/Nuke Studio session, import an image sequence that has non-sequential timecode (attached)
2) Drag this clip from the bin into the timeline to create a new sequence
3) With this clip in the timeline, right-click and select 'Effects > Text'
4) In the message field, type the following TCL to display the 'input timecode' metadata [metadata input/timecode]
5) Within the Viewer, drag the playhead through the clip range. Result: The timecode on the clip does not match the timecode extracted from the metadata
Expected behaviour The input timecode metadata should have interpreted the timecode into Nuke Studio/Hiero correctly.
Actual behaviour The input timecode metadata generated a different timecode based of the first frame of timecode of the source image sequence.
Workaround Unknown.
Reproduced by support This bug has been reproduced in: Hiero 12.2v5 - Windows 10 - CentOS7 - MacOS 10.15.6 Hiero 12.2v1 - Windows 10 Hiero 12.1v1 - Windows 10 Hiero 12.0v1 - Windows 10 Hiero 11.0v1 - Windows 10 Hiero 10.0v1 - Windows 10 Hiero 9.0v7 - Windows 10 - CentOS7 - MacOS
Unable to reproduce in: Hiero 1.9v1 - Windows 10 - CentOS7 - MacOS
Earliest version tested Hiero 1.9v1 - Not able to show TCL in timeline till Hiero 9.0v7