ID 557082 - DeepCrop bbox knobs return values that are off by one when expression linked with child parameters

Problem summary:
DeepCrop bbox knobs return values that are off by one when expression linked with child parameters
 
Customer reported version:
Nuke N/A
 
Customer reported platform:
N/A
 
Steps to reproduce:
1) Launch Nuke and create two DeepCrop nodes in the Node Graph.
2) In the first DeepCrop's Properties, set the bbox knob to values of your choice, such as the default format:

3) In the second DeepCrop's Properties, open the bbox knob's Animation menu and select Edit Expressions...
4) Link the two bbox knobs together with expressions that use child parameter names, such as DeepCrop1.bbox.x, DeepCrop1.bbox.y, etc.
5) Observe how the resulting values are off by one, and do not match their counterparts:  

 
Expected behavior:
Expression linked knobs should return the same value as the knob they are linked to.
 
Actual behavior:
Attempting to link the bbox knobs of two DeepCrop nodes will not result in identical values if the child parameter names are used.
 
Daisy chaining additional DeepCrop nodes will increment the off-by-one problem and produce larger discrepancies:

 
Workaround:
Instead of referencing the child parameters (.x, .y, etc.), only using the knob name (bbox) seems to create the expected result:

 
Reproduced by Support in:
Nuke 15.0v1 - Windows 10, macOS 13 Ventura
Nuke 14.1v1 - Windows 10, CentOS 7
Nuke 14.0v1 - Windows 10
Nuke 13.0v1 - Windows 10
Nuke 12.0v1 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.0v1 - Windows 10, CentOS 7
 
Earliest version tested:
Nuke 10.0v1 - This issue appears to be in all tested versions of the product