ID 369445 - Project with a Start Timecode of '23:59:50:00' has interaction problems when setting current timecode to '00:00:00:00'+

Problem summary
Timelines starting at 23:59:50:00 causes issues with setting the current timecode and importing footage starting past 00:00:00:00.

For example, when users receive timelines that have 10 seconds lead in, the sequence start at 00:00:00:00 the timeline will start at 23:59:50:00
Hiero & Nuke Studio handle this, and jump from  ->00:00:00:00 on a 24 fps feature.

But if you have a timeline that starts at 23:59:50:00 then you cannot use the "Set current timecode feature" as it will think that the timecode is before the start point.

Another example, the Playhead should move here ( Orange Timeline line ) when typing 00:00:00:00 in the highlighted timecode area: 

​

​​

It actually moves to 23:59:50:00, which is the incorrect behaviour.

​

Steps to reproduce

1) Open NukeStudio/Hiero, create a new Sequence.

2) Within the Sequence settings, set the 'Start Timecode' to '23:59:50:00'

3) Move the Timeline to a later position.

4) Set the 'Current Timecode' to '00:00:00:00'

Result: NukeStudio/Hiero current timecode will be set to '23:59:50:00', when it should be set to '00:00:00:00'

Workaround
Use a 'Start Timecode' of '00:00:00:00', start footage at '00:00:10:00' if you would like 10 seconds before the shot.

Reproduced by support

This bug has been reproduced in:
Nuke11.2v4 - Windows 7 - Mac10.13 - CentOS6.9
Nuke11.2v1 - Windows 7
Nuke11.1v4 - Windows 7
Nuke11.1v1 - Windows 7
Nuke11.0v4 - Windows 7
Nuke11.0v1 - Windows 7
Nuke10.5v7 - Windows 7 - Mac10.13 - CentOS6.9
Nuke10.5v1 - Windows 7
Nuke10.0v6 - Windows 7
Nuke10.0v1 - Windows 7
Nuke9.0v9 - Windows 7
Nuke9.0v1 - Windows 7
Nuke8.0v7 - Windows 7
Nuke7.0v10 - Windows 7 - Mac10.13 - CentOS6.9

Earliest version tested
- This issue appears to be in all versions of the product

Expected behaviour
When setting the timeline to '00:00:00:00' in a NukeStudio/Hiero project with a 'Start Timecode' of '23:59:50:00', the timeline should be set AFTER the timecode, not beforehand.

Actual behaviour
The current timecode is set beforehand, making it theoretically 23 hours out of place.