The Foundry Nuke Studio 13.0v1
The Foundry Nuke Studio 13.0v1 | 7.7 Gb
The Foundry is pleased to announce the availability of Nuke 13.0v1, the next feature release for Nuke. New version introduces flexible machine learning toolset, Hydra 3D viewport renderer and extended monitor out functionality, enhanced workflows for collaborative review, and Python 3 support.
Kicking off the next series of Nuke releases, Foundry has announced the release of Nuke 13. The release introduces a flexible machine learning toolset, a new Hydra 3D viewport renderer and extended monitor out functionality, enhanced workflows for collaborative review, and Python 3 support.
Developed by Foundry’s A.I. research team, Nuke 13 enables artists to create bespoke effects with a high-quality result in relatively little time. Applications of the flexible toolset include upres, removing motion blur, tracker marker removal, beauty work, and garbage matting. It allows artists to harness the power of machine learning directly in the software.
Key components of the machine learning toolset include:
CopyCat - An artist can create an effect on a small number of frames in a sequence and train a network to replicate this effect with the CopyCat node. This artist-focused shot-specific approach enables the creation of high-quality, bespoke models relatively quickly within Nuke without custom training environments, complex network permissions, or sending data to the cloud.
Inference - The node that runs the neural networks produced by CopyCat, applying the model to your image sequence or another sequence.
Upscale and Deblur - Two new tools for common compositing tasks were developed using the ML methodology behind CopyCat and open-source MLServer. The ML networks for these nodes can be refined using CopyCat to create even higher-quality shots or studio-specific versions in addition to their primary use for resizing footage and removing motion blur.
Nuke 13.0 also includes the introduction of Hydra support within Nuke’s 3D viewport, this offers a higher quality image much closer to Scanline Renderer’s output, enabling artists to work closer to their final image. Using hdStorm for rendering also provides a more consistent experience to other applications using Hydra.
Sync Review, originally Introduced in Nuke 12.2, has been extended to support syncing of editorial actions as well as playback and annotations. Now fully supported in Nuke Studio, Hiero, and HieroPlayer, Sync Review offers a new way to collaborate on review remotely and share the vision of the final image.
FeatureEnhancements
• BUG ID 158422/199269 - FrameHold: A new Set to Current Frame button has been added to the Properties panel.
• BUG ID 421243 - Nuke's Preferences > Project Defaults > Color Mangement options are now the same as Nuke Studio's, allowing you to set separate Default Color Transforms on a file type basis.
• BUG ID 453754 - Particles: The deprecated particleT attribute has been removed, resulting in a minor performance improvement. particleT was used to determine the age of the particle, but this information can be calculated from the particleStartTime attribute and the current time.
• BUG ID 457334 - CaraVR: The C_GenerateMap gizmo has been replaced by a plug-in for Nuke 13.0. This work includes the addition of a new Format control, which allows you to set the format of output ppass or stmaps when the node is not connected to a parent node. When the Source input is connected to any other node, the format is obtained from the parent node and the Format control is disabled.
BugFixes
• BUG ID 137121 - Nuke crashed on start up if the disk cache location set in the Preferences was no longer available.
• BUG ID 328844 - OFX: Inserting a CornerPin node after an OFX plug-in, such as Mocha Pro, occasionally caused Nuke to crash.
• BUG ID 333902 - Monitor Out: The Viewer gain and gamma controls did not affect the monitor display when Viewer GPU acceleration was enabled.
• BUG ID 349441 - Monitor Out: Switching from Kona3G card Monitor Out to floating window output caused Nuke to crash.
• BUG ID 379806 - Python: The Hiero example file spreadsheet_csv_export.py did not work as expected.
• BUG ID 401016 - Python: Calling Gizmo.filename() returned the value of a gizmo's file knob, rather than the gizmo's location on disk.
• BUG ID 401881 - Windows only: Custom shortcuts using Shift and keypad numbers could not be initialized.
• BUG ID 412043 - Windows only: Case mismatches in file paths were not handled as expected.
• BUG ID 419327 - DNxHD and DNxHR .mov files did not display different codec information in the Read node's Properties panel.
• BUG ID 431846 - Shuffle2: Expression linking Input or Output Layer controls to a channel control in another node caused Nuke to crash.
• BUG ID 431886 - Dragging files into the Project bin occasionally caused Nuke Studio and Hiero to become unresponsive.
• BUG ID 432704 - Shuffle2: Channels and layers that were not available were occasionally displayed in the Properties panel.
• BUG ID 433153 - UI: The overlay and guides menu was occasionally disabled if it included custom guides.
• BUG ID 438360 - Documentation: The NDK documentation for Setting up Projects and Compilers was out of date.
• BUG ID 441045 - Read/Write: DNxHR .mov files Imported into Nuke were identified incorrectly as DNxHD.
• BUG ID 447701 - macOS only: 3D Viewer rotation handles were drawn incorrectly on machines with certain GPUs.
• BUG ID 447820 - Deep: Viewing a DeepMerge node with deep.front and deep.back set to inf values caused Nuke to crash.
• BUG ID 448363 - BlinkScript: Creating unsigned variables using uint displayed an error when GPU acceleration was enabled.
• BUG ID 457741 - User Knobs: Adding multiple Group knobs in the Project Settings properties panel only created one endGroup knob.
• BUG ID 459491 - Read/Write: Reading DNx .mov files drew the Read node's Properties panel incorrectly.
• BUG ID 461787 - UI: The toolbar at the top of Nuke's Viewer was slightly larger in 3D mode than 2D mode.
• BUG ID 461854 - Read/Write: Reading legacy mov32 files using the mov64Reader displayed a persistent error in the timeline Viewer.
• BUG ID 463633 - Colorspace: Exporting a script with various output colorspaces displayed an Invalid LUT selected error.
• BUG ID 464353 - Median nodes did not produce the correct result at the edges of certain images.
• BUG ID 464372 - Python: Nuke cannot load movWriter from an external version of Python.
• BUG ID 464455 - Python: The foundrySG_Example.py example and documentation did not work as expected.
• BUG ID 464508 - Transform: Adjusting the scale control in a Transform node's Properties panel with show overscan active in the Viewer settings caused Nuke to crash.
• BUG ID 465012 - Python: FnFilenameField.py was missing an import of QtCore.QEvent and displayed errors in the console.
• BUG ID 465045 - Read/Write: The info bar overlay in Nuke Studio's Viewer displayed a one frame offset for .mov and .mxf files compared to the source timecode.
• BUG ID 465303 - Deep: Scripts with DeepRecolor nodes upstream of DeepToImage nodes caused Nuke to crash.
• BUG ID 465375 - Tags: Selecting shots with tags on the timeline was slow compared to shots without tags.
• BUG ID 467078 - Python: Renaming tags using the setName() function did not work as expected.
• BUG ID 468211 - UI: Dragging widgets between panes occasionally named tabs incorrectly
• BUG ID 158422/199269 - FrameHold: A new Set to Current Frame button has been added to the Properties panel.
• BUG ID 421243 - Nuke's Preferences > Project Defaults > Color Mangement options are now the same as Nuke Studio's, allowing you to set separate Default Color Transforms on a file type basis.
• BUG ID 453754 - Particles: The deprecated particleT attribute has been removed, resulting in a minor performance improvement. particleT was used to determine the age of the particle, but this information can be calculated from the particleStartTime attribute and the current time.
• BUG ID 457334 - CaraVR: The C_GenerateMap gizmo has been replaced by a plug-in for Nuke 13.0. This work includes the addition of a new Format control, which allows you to set the format of output ppass or stmaps when the node is not connected to a parent node. When the Source input is connected to any other node, the format is obtained from the parent node and the Format control is disabled.
BugFixes
• BUG ID 137121 - Nuke crashed on start up if the disk cache location set in the Preferences was no longer available.
• BUG ID 328844 - OFX: Inserting a CornerPin node after an OFX plug-in, such as Mocha Pro, occasionally caused Nuke to crash.
• BUG ID 333902 - Monitor Out: The Viewer gain and gamma controls did not affect the monitor display when Viewer GPU acceleration was enabled.
• BUG ID 349441 - Monitor Out: Switching from Kona3G card Monitor Out to floating window output caused Nuke to crash.
• BUG ID 379806 - Python: The Hiero example file spreadsheet_csv_export.py did not work as expected.
• BUG ID 401016 - Python: Calling Gizmo.filename() returned the value of a gizmo's file knob, rather than the gizmo's location on disk.
• BUG ID 401881 - Windows only: Custom shortcuts using Shift and keypad numbers could not be initialized.
• BUG ID 412043 - Windows only: Case mismatches in file paths were not handled as expected.
• BUG ID 419327 - DNxHD and DNxHR .mov files did not display different codec information in the Read node's Properties panel.
• BUG ID 431846 - Shuffle2: Expression linking Input or Output Layer controls to a channel control in another node caused Nuke to crash.
• BUG ID 431886 - Dragging files into the Project bin occasionally caused Nuke Studio and Hiero to become unresponsive.
• BUG ID 432704 - Shuffle2: Channels and layers that were not available were occasionally displayed in the Properties panel.
• BUG ID 433153 - UI: The overlay and guides menu was occasionally disabled if it included custom guides.
• BUG ID 438360 - Documentation: The NDK documentation for Setting up Projects and Compilers was out of date.
• BUG ID 441045 - Read/Write: DNxHR .mov files Imported into Nuke were identified incorrectly as DNxHD.
• BUG ID 447701 - macOS only: 3D Viewer rotation handles were drawn incorrectly on machines with certain GPUs.
• BUG ID 447820 - Deep: Viewing a DeepMerge node with deep.front and deep.back set to inf values caused Nuke to crash.
• BUG ID 448363 - BlinkScript: Creating unsigned variables using uint displayed an error when GPU acceleration was enabled.
• BUG ID 457741 - User Knobs: Adding multiple Group knobs in the Project Settings properties panel only created one endGroup knob.
• BUG ID 459491 - Read/Write: Reading DNx .mov files drew the Read node's Properties panel incorrectly.
• BUG ID 461787 - UI: The toolbar at the top of Nuke's Viewer was slightly larger in 3D mode than 2D mode.
• BUG ID 461854 - Read/Write: Reading legacy mov32 files using the mov64Reader displayed a persistent error in the timeline Viewer.
• BUG ID 463633 - Colorspace: Exporting a script with various output colorspaces displayed an Invalid LUT selected error.
• BUG ID 464353 - Median nodes did not produce the correct result at the edges of certain images.
• BUG ID 464372 - Python: Nuke cannot load movWriter from an external version of Python.
• BUG ID 464455 - Python: The foundrySG_Example.py example and documentation did not work as expected.
• BUG ID 464508 - Transform: Adjusting the scale control in a Transform node's Properties panel with show overscan active in the Viewer settings caused Nuke to crash.
• BUG ID 465012 - Python: FnFilenameField.py was missing an import of QtCore.QEvent and displayed errors in the console.
• BUG ID 465045 - Read/Write: The info bar overlay in Nuke Studio's Viewer displayed a one frame offset for .mov and .mxf files compared to the source timecode.
• BUG ID 465303 - Deep: Scripts with DeepRecolor nodes upstream of DeepToImage nodes caused Nuke to crash.
• BUG ID 465375 - Tags: Selecting shots with tags on the timeline was slow compared to shots without tags.
• BUG ID 467078 - Python: Renaming tags using the setName() function did not work as expected.
• BUG ID 468211 - UI: Dragging widgets between panes occasionally named tabs incorrectly
The Foundry Nuke Studio 13.0v1
The Nuke family consists of three different versions, Nuke, NukeX and Nuke Studio. Beyond the full compositing capabilities of NukeX, Nuke Studio includes a multi-track editorial timeline and full online editing toolkit. Nuke Studio enables onset editing, conforming online and the ability to bash out quick edits. Nuke Studio allows you to easily share timelines with artists using HieroPlayer, empowering artists to view shots in context, identify problems and challenge each other to be more creative. Efficiency and collaborative workflows are the core of the Nuke family. Whether working in a small team of artists or running an effects team, Nuke software makes teamwork seamless.
Break the boundaries of creativity with Nuke 13.0. With its new machine learning framework, implementation of a Hydra-powered 3D viewport, and extended SyncReview, Nuke 13.0 empowers artists. Gain more creative control, accelerate workflows, and get to the final pixel-perfect image quicker than ever before.
Nuke 13.0 | Overview
Foundry develops creative software for the digital design, media and entertainment industries. With a 20-year heritage and a portfolio of award-winning products, Foundry advances the art and technology of visual experience in partnership with creative leaders around the globe. Clients and partners include major feature film studios and post-production houses such as Pixar, ILM, MPC, Walt Disney Animation, Weta Digital, DNEG, and Framestore as well as automotive, footwear, apparel and technology companies such as Mercedes, New Balance, Adidas and Google.
Product: The Foundry NUKE
Version: 13.0v1
Supported Architectures: x64
Website Home Page : www.foundry.com
Language: english
System Requirements: PC / macOs / Linux *
Size: 7.7 Gb Gb
Qualified Operating Systems
- Windows 10 64-bit
- macOS Catalina (10.15.x) or macOS Big Sur (11.x)
- CentOS 7.4, 7.5, and 7.6 (64-bit)
Other System Requirements
- 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.
- 1 GB RAM (minimum requirement).
- 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.
- To enable Nuke to calculate certain nodes using the GPU, there are some additional requirements.
- R3D Rocket cards require the Rocket Driver 1.4.19.0 and Firmware 1.1.16.5 or later.
- Windows 10 64-bit
- macOS Catalina (10.15.x) or macOS Big Sur (11.x)
- CentOS 7.4, 7.5, and 7.6 (64-bit)
Other System Requirements
- 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.
- 1 GB RAM (minimum requirement).
- 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.
- To enable Nuke to calculate certain nodes using the GPU, there are some additional requirements.
- R3D Rocket cards require the Rocket Driver 1.4.19.0 and Firmware 1.1.16.5 or later.
Please visit my blog
Added by 3% of the overall size of the archive of information for the restoration
No mirrors please
![The Foundry Nuke Studio 13.0v1]()
Added by 3% of the overall size of the archive of information for the restoration
No mirrors please
The Foundry Nuke Studio 13.0v1
