Problem summary
QuickTime files rendered as mov32 do not export nclc data correctly within later Nuke 11.3 releases.
While there is no visual difference within Nuke, this causes issues with external programs that read this metadata and use to apply color variations.(e.g. RV)
This issue only occurs in Nuke 11.3v5 and later versions.
Customer reported version
nuke.12.0v1
Customer reported platform
windows10
Steps to reproduce
1) Open attached script in Nuke 11.3v4 (or earlier version) and render
2) Re-open attached script in Nuke 11.3v5 (or later version) and render
3) Open rendered QuickTime's and compare the results in the Viewer Result: No difference
4) Compare the metadata using a CompareMetadataNode Result: Nuke 11.3v5 does not have the same 'nclc_matrix' and 'nclc_primaries' data.
5) Open the rendered QuickTime's in RV and compare Result: The difference can be seen visually with Nuke 11.3v5 version darker.
Expected behaviour
QuickTime files that are mov32 should retain the correct nclc data for use in external programs
Actual behaviour
QuickTime files that are mov32 do not retain the correct nclc data for use in external programs
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
Nuke 12.0v1 - Windows 7 - MacOS 10.14.5
Nuke 11.3v5 - Windows 7 - MacOS 10.14.5
Unable to reproduce bug in:
Nuke 12.0v1 - CentOS 7 (mov32 was never created for Linux)
Nuke 11.3v4 - Windows 7 - MacOS 10.14.5
Earliest version tested
Nuke 11.3v4
- This issue doesn't appear in this version and has regressed