Problem summary Nuke Studio can incorrectly interpret retimed clips as full length clips from externally generated aaf files.
This issue only occurs in Nuke Studio 11 and later, and does not occur between other software packages when attempting the same process.
Customer reported version nuke.11.3v5
Customer reported platform centos7
Steps to reproduce
1) Open the attached aaf file in Nuke Studio
2) Open the attached aaf file in another aaf importing software package (Resolve, Premiere etc)
3) Compare the timelines between programs at 05:22:23:22 Result: The clip starting at the above timecode in Nuke Studio is the incorrect clip length
Expected behaviour The aaf file should retain the correct clip duration for all retimed clips
Actual behaviour The aaf does not retain the correct clip duration for some of the retimed clips
Workaround Unknown.
Reproduced by support This bug has been reproduced in: Nuke 11.3v5 - Windows 7 - CentOS 7 - MacOS 10.14.5 Nuke 11.3v1 - Windows 7 Nuke 11.2v1 - Windows 7 Nuke 11.1v1 - Windows 7 Nuke 11.0v1 - Windows 7 - CentOS 7 - MacOS 10.14.5
Unable to reproduce bug in: Nuke 10.5v7 - Windows 7 - CentOS 7 - MacOS 10.14.5
Earliest version tested Nuke 10.5v7 - This issue no longer appears in this version and has regressed