ID 525607 - Camera3 node renders incorrectly when changing the frame rate for alembic/abc files and using read from file

Problem summary
Camera3 node renders incorrectly when changing the frame rate for alembic/abc files and using read from file
 
Customer reported version
nuke.13.2v5
 
Customer reported platform
centos7
 
Steps to reproduce
 
1) Download the attached camera3RenderFail.nk and orbitCam.abc

2) Open Nuke and open camera3RenderFail.nk

3) Open the Camera node's Properties and set the path to that of orbitCam.abc
 
4) Scrub the timeline, the camera will orbit for 50 frames
 
5) Render the Write node using the frame server, frames 1-100
 
6) Read in the render, the camera orbits for 100 frames not 50, ignoring the frame rate set in the Camera node when rendered
 
*If you open the Nuke script with the path already set, then the camera will orbit for 100 frames, until you open the Camera node's properties, where it then seems to apply the frame rate change.
 
Expected behaviour
For the render to orbit for 50 frames:
 

 
Actual behaviour
The camera orbits for 100 frames, ignoring the frame rate set in the Camera node when rendered:

 
Workaround
Uncheck read from file when rendering the Nuke script.
Use the old Camera2 node
 
Reproduced by support
This bug has been reproduced in:
Nuke 13.2v5 - Windows 10, CentOS 7, macOS Monterey
Nuke 13.0v1 - Windows 10, CentOS 7, macOS Monterey
 
Earliest version tested
Nuke 13.0v1 - The Camera3 node did not exist before this version