Problem summary
Nuke reads R3D files differently depending on whether Cuda is being used or not and when using Cuda, artefacts appear.
Customer reported version
nuke.10.0v1
Customer reported platform
windows10
Steps to reproduce
1) On a Cuda compatible machine, open Nuke.
2) Create a Read node, reading in the footage: netqa/Testing/Nuke/FileIO/r3d/Attenborough_INT/L245_C001_07293P_001.R3D
3) Zoom into the shirt of the guy behind the clipboard, then toggle use cuda if available in the Read node otpions, and you will see the difference between it off and on, as shown in the screen shots below:
Reproduced by support
I have reproduced the issue in:
Nuke 9.0v1 Windows 10
Nuke 9.0v8 Windows 10
Nuke 10.0v1 Windows 10
Nuke 10.0v1 Linux CentOS 6.7
Nuke 10.0v1 Linux CentOS 6.7
Nuke 10.0v1 Linux CentOS 6.7
Expected behaviour
To see the same result when using Cuda to if not.
Actual behaviour
Using Cuda gave a different result to when not using it.
