State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:475165|
Problem summary
F_Align creates two keys when analyzing with the range knob set to Current frame.
Customer reported version
nuke.13.0v1
Customer reported platform
windows10
Steps to reproduce
1) In Nuke, read in footage for analyzing.
2) Add an F_Align node downstream, connecting the inputs.
3) Set the range knob for "Current frame", then analyze the footage.
Expected behavior
Only one keyframe should be created for the current frame.
Actual behavior
Two keys are created when analyzing with the F_Align node.
Workaround
There is no available workaround at this time.
Reproduced by Support in:
NukeX 13.01 - Windows 10, macOS 10.14
NukeX 12.2v1 - Windows 10
NukeX 12.1v1 - Windows 10
NukeX 12.0v1 - Windows 10
NukeX 11.0v1 - Windows 10
NukeX 10.0v1 - Windows 10
NukeX 9.0v1 - Windows 10
NukeX 8.0v1 - Windows 10, macOS 10.14
Earliest version tested
NukeX 8.0v1 - This issue appears to be in all versions of the product
We're sorry to hear that
Please tell us why