ID 591666 - AddTimeCode node doesn't use get FPS from metadata when setting the start time code, using 24 fps instead

Problem summary
AddTimeCode node doesn't use get FPS from metadata when setting the start time code, using 24 fps instead
 
Customer reported version
nuke.14.0v7
 
Customer reported platform
centos7
 
Steps to reproduce
 
1) Launch Nuke

2) Create a CheckerBoard node

3) Connect a AddTimeCode node, uncheck the  get FPS from metadata knob and set the fps knob to 60
 
4) Connect a second AddTimeCode node, and set the start code knob to 01:00:00:30 and view it
 
Expected behaviour
For the start time code to be set correctly
 
Actual behaviour
The second AddTimeCode node errors saying "Invalid start time code"
 
Workaround
Use an expression to drive the FPS knob:

AddTimeCode { startcode 01:00:00:30 fps {{"\[metadata input/frame_rate]"}} metafps false}

 
Reproduced by support
This bug has been reproduced in:
Nuke 15.1v4 - Windows 10, macOS Sonoma
Nuke 12.0v1 - Windows 10, macOS Sonoma
 
Earliest version tested
Nuke 12.0v1 - This issue appears to be in all tested versions of the product