ID 320730 - Nuke's default behavior for Writing Prores 422 codecs changes between operating systems

Problem summary
When setting a write node codec to Prores 422 on a machine CentOS 7.4 and then saving the script containing the node. It will change it's codec based on it's operating system. 

Customer reported version
nuke.11.0v2

Customer reported platform
centos7

Steps to reproduce

1) On a machine running Linux CentOS 7.4 launch any version of Nuke and create a simple script containing a checkerboard attached to a write node. 

2) On the write node set your properties to those of the following screenshot:

​

​

3) Save the script and open it in a different Operating System, (Windows 7/10, MacOSX 10.13) and you will see that the codec changes based on the Operating System. On MacOSX 10.13 the codec will default to "Apple ProRes 4444", and on Windows 7/10 it will default the codec "Motion JPEG A". 

Workaround
Write a python script to manually set the codec for a user created write node so its behavior does not change. 

Reproduced by support
Nuke 11.0v3 - Windows 7 - MacOS 10.13 Linux CentOS 7.4
Nuke 11.0v1 - Windows 7 - MacOS 10.13 Linux CentOS 7.4
Nuke 10.5v6 - Windows 7 - MacOS 10.13 Linux CentOS 7.4
Nuke 10.5v1 - Windows 7 - MacOS 10.13 Linux CentOS 7.4
Nuke 10.0v6 - Windows 7 - MacOS 10.13 Linux CentOS 7.4
Nuke 10.0v1 - Windows 7 - MacOS 10.13 Linux CentOS 7.4
Nuke 9.0v9 - Windows 7 - MacOS 10.13 Linux CentOS 7.4
Nuke 9.0v1 - Windows 7 - MacOS 10.13 Linux CentOS 7.4
Nuke 8.0v7 - Windows 7 - MacOS 10.13 Linux CentOS 7.4
Nuke 8.0v1 - Windows 7 - MacOS 10.13 Linux CentOS 7.4
Nuke 7.0v10 - Windows 7 - MacOS 10.13 Linux CentOS 7.4

Earliest version tested
Nuke 7.0v10

Expected behaviour
Nuke would use the same write node in the same codec across all machines
Actual behaviour
Nuke would change codecs across multiple OS's.