11 August 2020
Each chapter in this section explains in detail a key feature of Nuke.You can use the section to familiarize yourself with the features you are particularly interested in, or to get answers to specific problems that arise during compositing. By tuning into this session, you’ll get a good base on some of the technical structures in Nuke. At a time when we’re not able to get together, Foundry is pleased to host webinars across industry-wide topics, developments and releases that we believe are relevant to our user base and the broader VFX and digital design communities. Home The Foundry Visionmongers Limited is registered in England and Wales. Help Licensing help License compliance guide Activate a product Activate a Modo Serial Code User guides Maintenance Product Downloads Find a reseller Sitemap.
Warning:As a result of the current COVID-19 lockdown here in the UK, Foundry cannot guarantee that our usual high standards of QA have been applied to Nuke's monitor output functionality, including VR headset support, in this release.
• macOS Mojave (10.14) or macOS Catalina (10.15)
Note:We recommend macOS Mojave customers update to 10.14.6 to take advantage of performance enhancements.
• Windows 10 (64-bit)
• CentOS 7.4 (64-bit), or later
Note:The VFX Platform 2019 upgrade includes library versions that are only compatible with CentOS 7.4, or later. Nuke is qualified on the Centos 7.4, 7.5, and 7.6 distributions.
Other operating systems may work, but have not been fully tested.
Requirements for Nuke's GPU Acceleration
If you want to enable Nuke to calculate certain nodes using the GPU, there are some additional requirements.
NVIDIA
An NVIDIA GPU with compute capability 3.0 (Kepler) or above. A list of the compute capabilities of NVIDIA GPUs is available at https://developer.nvidia.com/cuda-gpus
Note:The compute capability is a property of the GPU hardware and can't be altered by a software update.
Sqlpro studio 1 0 302 – powerful database manager. With graphics drivers capable of running CUDA 10.1 or above. On Windows and Linux, CUDA graphics drivers are bundled with the regular drivers for your NVIDIA GPU. Driver versions 418.96 (Windows) and 418.39 (Linux), or above are required. See https://www.nvidia.com/Download/Find.aspx for more information.
Note:We recommend using the latest graphics drivers, where possible, regardless of operating system.
AMD
Note:Bit-wise equality between GPU and CPU holds in most cases, but for some operations there are limitations to the accuracy possible with this configuration.
• On Windows and Linux, an AMD GPU from the following list:
Note:Other AMD GPUs may work, but have not been fully tested.
• Radeon™ RX 480
• Radeon™ Pro WX 7100
• Radeon™ Pro WX 9100
• Radeon™ Pro SSG
• Radeon™ Pro WX 8200
Note:For information on the recommended driver for each GPU, see https://www.amd.com/en/support
• On Mac, AMD GPUs are supported on any late 2013 Mac Pro, mid 2015 MacBook Pros onward, and late 2017 iMac Pros.
Warning:Although AMD GPUs are enabled on other Mac models, they are not officially supported and used at your own risk.
Multi-GPU Processing
Nuke's GPU support includes an Enable multi-GPU support option. When enabled in the preferences, GPU processing is shared between the available GPUs for extra processing speed.
Note:Multi-GPU processing is only available for identical GPUs in the same machine. For example, two NVIDIA GeForce GTX 1080s or two AMD Radeon™ Pro WX 9100s.
There are no new features in this release.
There are no feature enhancements in this release.
• ID 410829 - Linux only: Creating a node from the Python interpreter shipped with Nuke caused the application to crash.
• ID 442968 - Nuke Indie: Adding a Keylight node to a script displayed a licensing error.
• ID 443058 - macOS only: Adjusting control sliders in Keylight's Properties panel occasionally caused Nuke to become unresponsive.
• ID 443268 - Launching Nuke Studio Non-commercial called for a full commercial license.
• ID 443488 - Read/Write: Using a relative file path in Read nodes failed if the ./ prefix was omitted from the string.
• ID 443628 - Licensing: Nuke set the RLM_ROAM environment variable on startup, rather than the foundry_ROAM environment variable, which also affected third-party RLM servers.
This section covers new known issues and gives workarounds for them, where appropriate.
Note:Changes to the way motion vectors are calculated in Nuke 12.2 cause any node using the Local option for motion estimation, such as Kronos and VectorGenerator, to render slightly different vectors when compared to legacy versions of Nuke. The default Regularized motion estimation method is unaffected.
• ID 444347 - Export: Presets that rely on mov32 do not populate the Content field in the Export dialog.
• ID 443296 - Windows only: The Nuke Indie icon is incorrect.
• ID 442165 - MOV: Writing out .mov files using the H.264 codec at resolutions above the 4K limit imposed by the codec causes Nuke to crash.
• ID 441979 - USD: Deselecting a group in the USD importer and then enabling view entire scenegraph does not load the group.
• ID 441555 - USD: Clicking Cancel in the USD import dialog and then enabling view entire scenegraph does not load the .usd file as expected.
• ID 441439 - R3D: Red decode CPU performance is slower in Nuke 12.2 compared to 12.1 builds.
• ID 440943 - USD: Expanding parent and children groups in the scenegraph manually does not create the horizontal scroll bar correctly.
As a workaround, right-click and select expand all to display the scroll bar.
As a workaround, right-click and select expand all to display the scroll bar.
• ID 440057 - Roaming: Hiero license roaming with a Nuke Studio license stack is not working as expected.
As a workaround, launch Nuke Studio and select License > Roaming and then set the Workspace to Conforming.
As a workaround, launch Nuke Studio and select License > Roaming and then set the Workspace to Conforming.
• ID 439958 - USD: The Transform tab controls are occasionally grayed-out for certain .usd files.
As a workaround, reload the .usd file.
As a workaround, reload the .usd file.
• ID 439011 - ApplyMaterial: Selecting filter > name and then clicking choose incorrectly displays Load state icons.
• ID 439002 - ApplyMaterial: Selecting filter > name and then clicking choose allows editing of the read-only names in the scenegraph.
• ID 436560/436551 - Sync Review: The formatting in the Sync Session panel and Host and Connect dialogs is inconsistent.
• ID 434956 - USD: Columns in the Scenegraph tab can only be rearranged once.
• ID 434574 - File Formats Update: Reading .mxf files in the HybridLogGamma colorspace defaults to linear incorrectly.
• ID 432438 - Vertex UV values are occasionally displayed incorrectly for .abc and .usd files.
• ID 430779 - File Formats Update: All deprecated IPP2 .r3d colorspaces appear the same as current colorspaces.
• ID 430760 - File Formats Update: DRAGONcolor2 and REDcolor4 use the same IPP2 .r3d colorspace.
• ID 429788 - macOS only: Legacy mov32 presets are no longer retained, choosing a preset always displays the Don't show this message dialog.
• ID 429658 - Sync Review: Dragging annotations does not update positions in sync sessions until the annotation is dropped.
• ID 429656 - Sync Review: Annotation markers in the timeline do not update automatically.
As a workaround, scrub the timeline to force the update.
As a workaround, scrub the timeline to force the update.
• ID 426901 - File Formats Update: In IPP2 Custom mode, enabling the Use GPU checkbox displays grading controls from the IPP2 Pipeline incorrectly.
Nuke Foundry Manual
Nuke Foundry Torrent
• ID 425200 - MOV: Legacy Write node Motion JPEG A/B files do not display the Quality control with mov64 selected as the encoder.
• ID 424070 - RIP: Ops requesting unused inputs occasionally prevent images being released from the device cache.
• ID 419327 - File Formats Update: DNxHD and DNxHR .mov files do not display different codec information in the Read node's Properties panel.
These pages guide you through installation and licensing to the point where you have the application in front of you and are ready to start work. After installation, all applications are run from either desktop icons, the browser, or from the command line using arguments.
Tip:For an overview of the documentation and quick access to the main topics, go to Nuke Home.
Qualified Operating Systems
• Windows 7 64-bit
• Windows 10 64-bit
Note:Other operating systems may work, but have not been fully tested.
• x86-64 processor, such as Intel Pentium 4 or AMD Athlon, with SSE3 instruction set support (or newer).
• 5 GB disk space available for caching and temporary files.
• At least 8 GB of RAM.
• Display with at least 1280 x 1024 pixel resolution and 24-bit color.
• Graphics card with at least 512 MB of video memory and driver support for OpenGL 2.0 (minimum requirement).
• To enable optional GPU acceleration of Viewer processing, you need OpenGL 2.0 with support for floating point textures and GLSL. Keycue 9 78.
• To enable Nuke to calculate certain nodes using the GPU, there are some additional requirements. For more information, see Requirements for GPU Acceleration.
• R3D Rocket cards require the Rocket Driver 1.4.19.0 and Firmware 1.1.16.5 or later.
Note:To avoid graphical problems, such as text disappearing in the Viewer and Node Graph , it is important to keep your graphics card drivers up-to-date. Driver updates can be obtained from the websites of the graphics card manufacturers (for example, www.nvidia.com and support.amd.com).
Note:If you’re using R3D Rocket graphics card, note that using it with Foundry applications will most likely only be considerably faster when you’re reading in at full resolution. If you’re reading in at half resolution, for instance, disabling the R3D Rocket card may be faster. This is because the R3D Rocket graphics card is designed to be fast when reading in multiple frames at the same time. This is not how Nuke works internally, and therefore reads with the R3D Rocket card disabled may sometimes be faster when working in lower resolutions (< 4K widths). Note that the R3D Rocket card always produces better results than Nuke when downsampling. Also, the R3D Rocket card can only be used by one application at a time, so if you are viewing multiple Nuke comps at once, you may only be able to use the R3D Rocket card in one.
If you want to enable Nuke to calculate certain nodes using the GPU, there are some additional requirements.
NVIDIA
• An NVIDIA GPU with compute capability 3.0 (Kepler) or above. A list of the compute capabilities of NVIDIA GPUs is available at www.nvidia.co.uk/object/cuda_gpus_uk.html
Note:The compute capability is a property of the GPU hardware and can't be altered by a software update.
• On Windows, driver versions 418.96 , or above is required.
Go to http://www.nvidia.com/Download/Find.aspx?lang=en-us for more information.
Note:If your computer enters sleep mode, the CUDA drivers cannot recover and you must restart Nuke to use GPU acceleration.
Nuke Compositing Software
Tip:We recommend using the latest graphics drivers, where possible.
AMD
Note:Bit-wise equality between GPU and CPU holds in most cases, but for some operations there are limitations to the accuracy possible with this configuration.
An AMD GPU from the following list:
Note:OpenCL must be installed for Nuke to enable AMD GPUs.
• Radeon™ RX 480
Nuke Foundry Youtube
• Radeon™ Pro WX 7100
• Radeon™ Pro WX 9100
• Radeon Pro WX 8200
• Radeon Pro W5700
Note:Other AMD GPUs may work, but have not been fully tested. We recommend using the latest graphics drivers, where possible. For information on the recommended driver for each GPU, see https://www.amd.com/en/support
Multi-GPU Processing
Imagenomic professional plugin suite for adobe photoshop 1720. Nuke's GPU support includes an Enable multi-GPU support option. When enabled in the preferences, GPU processing is shared between the available GPUs for extra processing speed.
Note:Multi-GPU processing is only available for identical GPUs in the same machine. For example, two NVIDIA GeForce GTX 1080s or two AMD FirePro W9100s.