Problem summary
Nuke is encountering an instant crash when reading in Rec.2020 (also known as BT.2020) QuickTime formats that use SMPTE's ST.2084 encoding settings. Reading in this file format into Nuke will cause a segfault crash. The cause of the problem appears to not be the image data, but rather the metadata associated to encoded format.
This has varied results over different operating systems and Nuke releases, which I have added in the reproduction documentation below.
In general the codec crashes in MacOS (10.13 tested) and Windows (7 Pro tested), although no crash occurs in Linux (CentOS 6.9) and in all current release versions after and including Nuke 8.0v1.
Through verbose logging you will receive the following error (shown in Mac environment):
Loading /Applications/Nuke11.1v1/Nuke11.1v1.app/Contents/MacOS/plugins/movReader.dylib0 QuickTimeHelper-32 0x000055e7 QuickTimeHelper-32 + 17895Segmentation fault: 11
Customer reported version
nuke.11.1v1
Customer reported platform
10.10
Steps to reproduce
Open the attached QuickTimes to compare and confirm.
OR
1) Import a 'ST.2084/BT.2020' file into a Mac or Windows environment
Result: Crashing due to a segmentation fault
Workaround
As the metadata is causing the issue, one option is to strip the metadata from the QuickTime file. This can be achieved through stripping the data using a QuickTime file parameter editor.
After stripping the metadata, the color information can be reproduced through the use of colorspace nodes to rebuild the lost color information within Nuke.
Reproduced by support
This bug has been reproduced in:
Nuke 11.1v1 - MacOSX 10.13 - Windows 7
Nuke 11.0v3 - MacOSX 10.13 - Windows 7
Nuke 10.5v7 - MacOSX 10.13 - Windows 7
Nuke 10.5v1 - MacOSX 10.13 - Windows 7
Nuke 10.0v6 - MacOSX 10.13 - Windows 7
Nuke 10.0v1 - MacOSX 10.13 - Windows 7
Nuke 9.0v9 - MacOSX 10.13 - Windows 7
Nuke 9.0v1 - MacOSX 10.13 - Windows 7
Nuke 8.0v7 - MacOSX 10.13 - Windows 7
Nuke 8.0v1 - MacOSX 10.13 - Windows 7 - regression
Unable to reproduce bug in:
Nuke 11.1v1 - Centos 6.9
Nuke 11.0v3 - Centos 6.9
Nuke 10.5v7 - Centos 6.9
Nuke 10.5v1 - Centos 6.9
Nuke 10.0v6 - Centos 6.9
Nuke 10.0v1 - Centos 6.9
Nuke 9.0v9 - Centos 6.9
Nuke 9.0v1 - Centos 6.9
Nuke 8.0v7 - Centos 6.9
Nuke 8.0v1 - Centos 6.9
Nuke 7.0v9 - MacOSX 10.13 - Windows 7 - Centos 6.9
Earliest version tested
Nuke 7.0v9
- This issue no longer appears in this version and has regressed
Expected behaviour
Reading in this format should not cause a segmentation crash, it should alternatively create an unsupported codec error.
Actual behaviour
Reading in this codec format is causing a segmentation crash