ID 286831 - Unable to write 120 fps renders with 'Apple ProRes' codecs

Problem summary
When a user chooses to export a 'mov' file with a 'ProRes 422' codec, If they change the fps to any value over 60 fps and check mark the 'write time code' option, the export may break and become unusable.

It exports as expected on Windows 7, but it breaks on CentOS6.9 systems & Mac10.12.

It may be a codec issue, I have had mixed results on Mac with our laptop (Mac10.12) breaking renders yet the Mac PC (Mac10.12)  exporting correctly

This error appears when the render breaks:
[mov @ 0x7fa980000d60] Timecode frame rate 0/0 not supported

Customer reported version
nuke.10.5v3

Customer reported platform
centos6

Steps to reproduce

1)  Launch Nuke - Read in a sequence of images.

2)  Add a Write node to the Read node.

3) In the Write node, Set the FileType to 'mov', Codec to 'Apple ProRes 442 HQ', fps to '120', Check the 'write time code' Checkbox.

4) Render the 'mov' file.

Result) An error log will appear after the render is complete and the file will not open (The file size is only a few bytes.)

Workaround
Before rendering your shot, uncheck the 'write time code' option and render.
It should export as expected.

Reproduced by support
Works Correctly:
Nuke11.0v1 - Windows 7
Nuke10.5v5 - Windows 7
Nuke10.5v3 - Windows 7
Nuke10.5v1 - Windows 7
Nuke10.0v6 - Windows 7
Nuke10.0v1 - Windows 7
Nuke9.0v9 - Windows 7
Nuke9.0v1 - Windows 7

Breaks:
Nuke11.0v1 -Mac 10.12 - CentOS6.9
Nuke10.5v5 -Mac 10.12 - CentOS6.9
Nuke10.5v3 -Mac 10.12 - CentOS6.9
Nuke10.5v1 -Mac 10.12 - CentOS6.9
Nuke10.0v6 -Mac 10.12 - CentOS6.9
Nuke10.0v1 -Mac 10.12 - CentOS6.9
Nuke9.0v9 -Mac 10.12 - CentOS6.9
Nuke9.0v1 -Mac 10.12 - CentOS6.9

Earliest version tested

Nuke9.0v1 - Apple ProRes codecs aren't available on earlier versions.

Expected behaviour
File exports at chosen value over 60fps, video file works correctly. 

Actual behaviour
On Mac & Linux. The render will break, send a log and the video file will be un-playable.