Problem summary
When rendering as a QuickTime mov format using a mov64-based codec, the timecode metadata will not be written into the rendered file.
These mov64 codecs include:
Animation Apple ProRes (all) Avid DNxHD MPEG-1 Video MPEG-4 Video Motion JPEG B PNG Photo - JPEG Uncompressed 10-bit 4:2:2 Note: This issue
only occurs in Nuke 12.1v1 releases and later.
Customer reported version
nuke.12.1v1
Customer reported platform
10.14
Steps to reproduce
1) Open a new Nuke 12.1 release session
2) Create a
CheckerBoard node
3) Create an
AddTimeCode node, connecting it to the
CheckerBoard node
4) Create a
ViewMetaData node, connecting it to the
AddTimeCode node
5) View the results of the
ViewMetaData node and note the 'input/timecode' value
6) Create a new
Write node
7) Within the
Write node properties:
a) select a render location
b) select 'mov' as the 'file type'
c) set the codec to a mov64 based codec (eg. Apple ProRes 4444)
d) toggle the 'write time code' checkbox on
e) Render
8)
Read the exported QuickTime mov back into the Nuke session
9) Create another
ViewMetaData node and view the results
Results: No 'input/timecode' metadata exists within the rendered QuickTime mov file.
Expected behaviour
When the 'write time code' checkbox is enabled, a mov64 based codec should write the timecode as metadata into the rendered QuickTime file
Actual behaviour
When the 'write time code' checkbox is enabled, the timecode is not rendered into the exported QuickTime file if the codec is mov64-based.
Workaround
Unknown.
Reproduced by support
This bug has been reproduced in:
Nuke 12.1v1 - Windows 10 - MacOS 10.14.6 - CentOS 7 - regression
Unable to reproduce bug in:
Nuke 12.0v5 - Windows 10 - MacOS 10.14.6 - CentOS 7
Earliest version tested
Nuke 12.0v5
- This issue doesn't appear in this version and has regressed