ID 534720 - ARRI RAW Alexa 35 timecode metadata is off by -1 frame when read in Nuke Studio

Follow

Problem summary:
ARRI RAW Alexa 35 timecode metadata is off by -1 frame when read in Nuke Studio
 
Customer reported version:
Nuke Studio 14.0v2
 
Customer reported platform:
Windows 10
 
Steps to reproduce:
1) Launch Nuke Studio and navigate to File > Import File(s)...
2) Select an ARRI RAW Alexa 35 file to Open.
3) Add the footage to a Sequence by dragging it to the Timeline from the Project Bin.
4) Right-click on the clip in the Timeline and select Soft Effects > Text
5) In the Properties Panel, paste the following into the Text Soft Effect's message field:
Frame: [metadata input/frame]TC: [metadata input/timecode]
6) Switch to the Node Graph tab, and create a Read node by dragging the footage into the empty space.
7) Create a Text node and add the same message from step 5.
8) Compare the Text node with the Text Soft Effect, pictured below:

Expected behavior:
Nuke Studio should read the timecode of ARRI RAW Alexa 35 footage correctly in the Timeline, and be consistent with the Node Graph.
 
Actual behavior:
The timecode values of ARRI RAW Alexa 35 footage are offset by -1 frame in the Timeline and do not match the Node Graph's correct values.
 
Workaround:
No known workaround at this time.
 
Reproduced by Support in:
Nuke Studio 14.0v2 - Windows 11, CentOS 7
Nuke Studio 14.0v1 - Windows 11, CentOS 7
 
Earliest version tested:
Nuke 14.0v1 - This feature (support for the ARRI Alexa 35/ARRI IMAGE 7.0.0 SDK) did not exist before this version.

    We're sorry to hear that

    Please tell us why