State:New|TargetRelease:No Target|icon_bug|icon_nuke|database:public|Resolution:Fixed|BugID:155349|
Problem summary
Write nodes exporting a .mov file in a Nuke script saved on Linux may have the wrong codec set when the script is opened on a Windows or MacOSX machine.
Steps to reproduce
On a Linux machine, launch Nuke and create a Write node.
Set the file knob to /tmp/test.mov.
Note that the codec is set to 'Apple ProRes 4444'.
Save the script.
Open the script on a machine running Windows or MacOSX.
Expected behaviour
The codec knob on the Write node is still set to ‘Apple ProRes 4444’
Actual behaviour
The codec is set to ‘Motion JPEG A’ on MacOSX and Windows (‘MPEG-4 video’ if QuickTime is not installed and 'Motion JPEG A' isn't available).
Workaround
Unknown
Reproduced by support
Nuke 11.2v3 - CentOS 6.9 to Windows 10/MacOSX 10.13.5 (High Sierra)
Nuke 11.2v1 - CentOS 6.9 to MacOSX 10.13 (High Sierra)
Nuke 11.1v5 - CentOS 6.9 to MacOSX 10.13 (High Sierra)
Nuke 11.1v1 - CentOS 6.9 to MacOSX 10.13 (High Sierra)
Nuke 11.0v4 - CentOS 6.9 to MacOSX 10.13 (High Sierra)
Nuke 11.0v1 - CentOS 6.9 to MacOSX 10.13 (High Sierra)
Nuke 10.5v7 - CentOS 6.9 to MacOSX 10.13 (High Sierra)
Nuke 10.0v6 - CentOS 6.9 to Windows 10/MacOSX 10.13 (High Sierra)
We're sorry to hear that
Please tell us why