Problem summary
Mov64 codec fails to encode 24 bit audio when rendering with a write node in Nuke.
Customer reported version
nuke.10.5v3
Customer reported platform
Centos6
Steps to reproduce
1) Open Nuke
2) Create a checkerboard
3) Create and attach a write node to the checkerboard
4) In the "file" path of the write node, specify a path for the file to write and a file name with the extension ".mov". I.e. C:/Users/<user>/Desktop/testAudio16bit.mov
5) In the "mov Options" section point the audio file path to a 16 bit audio file.
6) Duplicate this network.
7) In the duplicated write node, rename the file to "testAudio24bit.mov" from "testAudio16bit.mov"
8) Point the audio file path to a 24 bit audio file.
9) Render both write nodes.
Result: the 16 bit file renders fine, the 24 bit file aborts with the error "Write2: failed to open the audio file - It does not contain audio or is an invalid file"
Workaround
24 Bit audio renders fine in mov32.
1) Type "mov32:" before the file path i.e. "mov32:C:/Users/<user>/Desktop/testAudio24bit.mov"
Note: This forces the mov32 codec rather than mov64.
2) Repoint the audio file path to the 24 bit audio file (this field is cleared when changing to mov32)
3) Render the file.
Result: File renders with 24 bit audio.
Reproduced by support
Encode of 24 bit audio fails:
10.5v4 - Windows 10, Centos 6.9, Osx 10.12.5
10.5v3 - Windows 10
10.5v1 - Windows 10, Osx 10.12.5
10.0v6 - Windows 10, Centos 6.9, Osx 10.12.5
10.0v1 - Windows 10, Osx 10.12.5, Osx 10.12.5
9.0v9 - Windows 10, Centos 6.9, Osx 10.12.5
9.0v1 - Windows 10, Centos 6.9, Osx 10.12.5
24 bit audio encodes properly:
8.0v7 - Windows 10, Osx 10.12.5
8.0v1 - Windows 10, Osx 10.12.5
7.0v10 - Windows 10
7.0v1 - Windows 10
Expected behaviour
24 bit audio renders out when rendering in .mov format.
Actual behaviour
24 bit audio causes render to fail in .mov (mov64) format. Works fine in mov32.