12/1/2020 Nuke Foundry
Product Forums Product Forums Back Nuke Hiero Katana Modo Mari Cara VR Colorway Flix. Student Area Plug-Ins Kits & Training Related Interests Search. Nuke Studio's timeline is designed to provide shot management, conform, playback, and export capabilities for people creating visual effects. Advanced Compositing A specialized toolkit of exclusive time-saving features, ideal for taking on more complex compositing tasks, including a selection of the award-winning Furnace tools.
NUKE is a node-baseddigital compositing and visual effectsapplication first developed by Digital Domain, and used for television and film post-production. NUKE is available for Microsoft Windows 7, OS X 10.9, Red Hat Enterprise Linux 5, and newer versions of these operating systems.[2] The Foundry has further developed the software since Nuke was sold in 2007.
NUKE's users include Digital Domain, Walt Disney Animation Studios, Blizzard Entertainment,[3]DreamWorks Animation,[4]Illumination Mac Guff,[5]Sony Pictures Imageworks, Sony Pictures Animation, Framestore,[6]Weta Digital,[7]Double Negative,[8] and Industrial Light & Magic.[9]
History[edit]
NUKE (the name deriving from 'New compositor')[10] was originally developed by software engineer Phil Beffrey and later Bill Spitzak for in-house use at Digital Domain beginning in 1993. In addition to standard compositing, NUKE was used to render higher-resolution versions of composites from Autodesk Flame.[11]
NUKE version 2 introduced a GUI in 1994, built with FLTK – an in-house GUI toolkit developed at Digital Domain. FLTK was subsequently released under the GNU LGPL in 1998.[12]
NUKE won an Academy Award for Technical Achievement in 2001.[13]
In 2002, NUKE was made available to the public for the first time under the banner of D2 Software.[14][15] In December 2005, D2 Software released NUKE 4.5,[16] which introduced a new 3D subsystem developed by Jonathan Egstad.[17]
In 2007, The Foundry, a London-based plug-in development house, took over development and marketing of NUKE from D2.[18] The Foundry released NUKE 4.7 in June 2007,[19] and NUKE 5 was released in early 2008, which replaced the interface with Qt and added Python scripting, and support for a stereoscopic workflow.[20] In 2015, The Foundry released NUKE Non-commercial with some basic limitations.[21] NUKE supports use of The Foundry plug-ins via its support for the OpenFX standard (several built-in nodes such as Keylight are OpenFX plugins).
Similar products[edit]
While not dedicated to compositing, the open source software Blender contains a limited node-based compositing feature which, among other things is capable of basic keying and blurring effects.[22]
References[edit]
External links[edit]
Retrieved from 'https://en.wikipedia.org/w/index.php?title=Nuke_(software)&oldid=964253481'
![]()
11 August 2020
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.
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.
Nuke Foundry Tutorial
• 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.
• 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.
• ID 439958 - USD: The Transform tab controls are occasionally grayed-out for certain .usd files.
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.
![]() The Foundry Nuke Studio Portable
• 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.
Nuke Foundry
• ID 429656 - Sync Review: Annotation markers in the timeline do not update automatically.
As a workaround, scrub the timeline to force the update. Nuke Foundry Download
• ID 426901 - File Formats Update: In IPP2 Custom mode, enabling the Use GPU checkbox displays grading controls from the IPP2 Pipeline incorrectly.
Foundry Nuke Free
• 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.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |