Problem summary
When using the 'Frame' timing option within the Nuke Kronos node, the 'Source' frames will be flipped with the 'MoSrc' in the viewer if the reference frame is '1' frame before the current frame.
If the reference frame is '2' before the current frame, the sources aren't flipped.
Additionally, if the reference frame is '1' after the current frame, the sources aren't flipped.
This bug does not appear to happen with the Furnace equivalent 'F_Kronos 402'.
Customer reported version
nuke.11.1v1
Customer reported platform
n_a_windows
Steps to reproduce
1) Read in your Kronos Footage and reference.
2) Attach your Kronos footage to a Kronos node (Main on 'Source', Reference on 'MoSrc')
3) Within the Kronos node, switch the 'Timing' to 'Frame'.
4) Through your footage, set keys for your Reference footage one frame before the Keyed frame.
5) Play through the footage.
Result: Your main footage ('Source') should be replaced with your reference footage ('MoSrc').
Workaround
Unknown
Reproduced by support
This bug has been reproduced in:
Nuke11.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke11.0v4 - Windows 7 - Mac10.12 - CentOS6.9
Nuke11.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.5v7 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.5v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.0v6 - Windows 7 - Mac10.12 - CentOS6.9
Nuke10.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke9.0v9 - Windows 7 - Mac10.12 - CentOS6.9
Nuke9.0v1 - Windows 7 - Mac10.12 - CentOS6.9
Nuke8.0v7 - Windows 7 - Mac10.12 - CentOS6.9
Unable to reproduce bug in:
Nuke7.0v10 - Windows 7 - Mac10.12 - CentOS6.9
Earliest version tested
- Nuke7.0v10 - This issue no longer appears in this version and has regressed (Node is older than the current node)
Expected behaviour
Setting a reference frame 1 frame before the current frame should not cause the 'MoSrc' to replace the 'Source'
Actual behaviour
The 'MoSrc' replaces the 'Source' when one frame before the current frame