# Nuke at school

# Nuke - What's different at school?

If you've used Nuke before you'll probably be familiar with the many ways it can be customized and the huge amount of gizmos and tools available online. Nuke at school comes with many of these customizations pre-configured for you.

### Color management

Color management is globally configured for all our applications at school. You'll see this when you open your Nuke project settings and go to the Color tab:

[![image.png](https://docs.vfxim.nl/uploads/images/gallery/2026-11/scaled-1680-/h7Eimage.png)](https://docs.vfxim.nl/uploads/images/gallery/2026-11/h7Eimage.png)

Don't change these settings! It's important they stay configured like this so Nuke plays nicely with the colors in our renders and the footage we get from our editors. Colorspace theory is taught in the second year.

### Gizmos and tools

All our gizmos/tools can be found in the side bar when you click on the NFA logo. They'll also show up in your tab search.

![Nuke15.0_VRpTE9JcyZ.png](https://docs.vfxim.nl/uploads/images/gallery/2024-10/scaled-1680-/nuke15-0-vrpte9jcyz.png)

As you can see we have quite a large selection available. Check out [this page](https://docs.vfxim.nl/books/nuke-at-school/page/nuke-custom-tools) for an overview of tools made by our students!

It's not possible for you to install new gizmos yourself because of how our Nuke is customized from one central location. Gizmo/tool installation is typically done by more TD inclined students, as it involves a bit of Git version control. Instructions for this can be found in the TD section of this documentation. You can technically install plugins and gizmos in your own `.nuke` user folder, but keep in mind that your render will likely fail on the farm when you do this.

Two tools worth mentioning are Reduce Noise V6 by NeatVideo and OpenDefocus by Gilles Vink (an NFA alumni!).

### Render farm

At school we have a render farm at our disposal which you can use to render your comps. Check out [this page](https://docs.vfxim.nl/books/nuke-at-school/page/nuke-rendering-on-the-farm) on how to submit your renders.

# Nuke - Rendering on the farm

Submitting your comp to our render farm is quite easy. First make sure that all the files used in your comp (and your Nuke file itself, of course) are stored on our Storage server. Then select the Write node you want to render and click *Render &gt; Submit to Deadline* in the menu bar, or press **F5**. The *render on farm* button on a ShotGrid write node opens the same window.

[![Schermafbeelding 2026-11-16 164933.png](https://docs.vfxim.nl/uploads/images/gallery/2026-11/scaled-1680-/schermafbeelding-2026-11-16-164933.png)](https://docs.vfxim.nl/uploads/images/gallery/2026-11/schermafbeelding-2026-11-16-164933.png)

Most of the time you only have to check the name, the frame range and the mode, and press *OK*.

### Job

- **Submission name:** the name of your job in the Deadline Monitor. Filled in with your script name.
- **Comment:** shown in the Comment column of the Monitor. Optional.
- **Department:** just a label, you can leave it on 2D.

### Render

- **Priority:** jobs with a higher priority are picked up first when a PC is free. Leave it at 70 unless you've agreed on a different number with your [render managers](https://docs.vfxim.nl/books/deadline-at-school/page/deadline-render-managers).
- **Submit suspended:** the job waits in the queue until you resume it in the Monitor.
- **Frame range:** *global* uses your project frame range, *input* the frame range of the Write node, and *in-out* the in and out points of your viewer. You can also just type a range.
- **Mode:** how much one PC renders at the same time (see below).
- **Enable smart frame spreading:** renders the first frame first, then the last, then the middle, and then fills in the gaps evenly. Handy for a long render when you want to know quickly whether it renders all the way through.

### Modes

One PC on the farm can render several tasks of your job at the same time. The mode decides how many:

- **light:** 10 tasks at once on a PC, 3 frames per task
- **medium:** 5 tasks at once, 2 frames per task
- **heavy:** 1 task at a time, 1 frame per task
- **custom:** type your own numbers

A light render is a lot faster, but a heavy comp in light mode makes PCs run out of memory and crash. That's why the submitter *suggests* a mode: it looks at the nodes that feed your Write (how many there are, and whether there are 3D renders, deep or retimes) and picks that mode for you. Next to the mode you can see why, for example *suggested · 3D render, deep*. Nothing is rendered for this, so it's a guess; you can always pick another mode.

Do your renders still crash with memory errors? Choose a heavier mode. The farm also does this by itself after a few crashes, see [ErrorTriage](https://docs.vfxim.nl/books/deadline-at-school/page/deadline-event-plugins).

Rendering a movie (.mov, .mp4, ...)? A movie can't be split over several PCs, so the whole range renders as one task on one PC, and the mode is hidden. This is much slower than rendering an image sequence: for long or heavy renders, render EXRs and make the movie afterwards.

### Farm

- **Pool:** only PCs in this pool render your job. Leave it on *none* unless you've agreed otherwise with your render managers. For example, *128gb* only renders on the PCs with 128 GB memory, for very heavy comps.
- **Secondary pool:** PCs in this pool pick up your job when the PCs of the first pool are busy.
- **Group:** leave this on *none*.

### More options

Click *More options* for the settings you'll rarely need.

[![Schermafbeelding 2026-11-16 164926.png](https://docs.vfxim.nl/uploads/images/gallery/2026-11/scaled-1680-/schermafbeelding-2026-11-16-164926.png)](https://docs.vfxim.nl/uploads/images/gallery/2026-11/schermafbeelding-2026-11-16-164926.png)

- **Use GPU:** lets GPU nodes (ZDefocus, Kronos, BlinkScript, Inference, ...) use the graphics card instead of the processor. On by default. Turn it off when a GPU-heavy script crashes on the farm: all tasks on a PC share one graphics card.
- **Machine limit:** the most PCs that render your job at the same time. 0 = no limit.
- **Machine list:** only these PCs render your job, or with *Machine list is a deny list* on: these PCs never render it. Use *Pick...* to choose them from a list.
- **Wait for jobs:** your job only starts when these jobs have finished, for example the Houdini render you're comping. Use *Pick...* to choose from your jobs.
- **Task timeout (min):** a task that renders longer than this is stopped and tried again. 0 = no limit.
- **On job complete:** *Archive* or *Delete* removes the job from the Monitor when it's done. Your rendered files are not touched.

### Checks before submitting

When you press *OK*, the submitter checks your script for the most common reasons a render fails on the farm:

- Your script has to be saved on the storage or education server. If it has unsaved changes, it asks to save it.
- Read nodes or a Write node with a local path (like C:\\ or your desktop), and Read nodes with errors: you get a warning and can still choose to submit.
- Proxy mode on without a proxy path on the Write: it offers to turn proxy mode off.
- MagicDefocus is not supported on the farm: replace it with OpenDefocus. Disabled MagicDefocus nodes are fine.
- NeatVideo nodes: we only have a limited number of licenses, so your job gets a license limit. See [LicenseLimiter](https://docs.vfxim.nl/books/deadline-at-school/page/deadline-event-plugins).
- Frames that already exist in your output folder: it tells you which ones, so you don't overwrite a render by accident.

After submitting, your job shows up in the Deadline Monitor. If something goes wrong during the render, check the job comment first; our [event plugins](https://docs.vfxim.nl/books/deadline-at-school/page/deadline-event-plugins) explain there what happened.

<span style="color: rgb(126, 140, 141);">Deadline submission tools by Gilles Vink, updated by Robbert Scholten</span>

# Nuke - Custom tools

Over the years our students have made a lot of nice additions to our Nuke. Here's a showcase of some of these tools.

#### AssetBrowser - By Robbert Scholten

Our AssetBrowser is the easiest way to use our ActionVFX elements directly in your Nuke scripts. You can easily search, favorite and see video previews of all our assets.

[![image.png](https://docs.vfxim.nl/uploads/images/gallery/2026-11/scaled-1680-/image.png)](https://docs.vfxim.nl/uploads/images/gallery/2026-11/image.png)

#### Snippets - By Gilles Vink

The snippets tool, which can be found in the top menu bar, makes it easy to store a part of your node graph so other Nuke users can load it into their comp. Just select the nodes you want to save, press "Create snippet" and give it a name. It will show up for other users under your own name.

[![Nuke15.0_i6wj2XooFX.png](https://docs.vfxim.nl/uploads/images/gallery/2024-10/scaled-1680-/nuke15-0-i6wj2xoofx.png)](https://docs.vfxim.nl/uploads/images/gallery/2024-10/nuke15-0-i6wj2xoofx.png)

#### Node Mailer - By Mervin van Brakel

Node Mailer allows you to "mail" node setups to other students that have Nuke open at school. They will receive a pop-up notification that allows them to import the selected nodes you've sent.

[![Nuke15.0_ahxmS8bf5l.png](https://docs.vfxim.nl/uploads/images/gallery/2025-01/scaled-1680-/nuke15-0-ahxms8bf5l.png)](https://docs.vfxim.nl/uploads/images/gallery/2025-01/nuke15-0-ahxms8bf5l.png)

#### LightGroupMixer - By Mervin van Brakel

The LightGroupMixer gizmo goes through the layers of your CG render and collects light groups for you to grade. This only works if your light group layer names have the prefix `LG_`, which is done automatically in our ShotGrid pipeline.

[![output.gif](https://docs.vfxim.nl/uploads/images/gallery/2024-10/output.gif)](https://docs.vfxim.nl/uploads/images/gallery/2024-10/output.gif)

#### Extract Camera from CG render - By Max de Groot

Found in the Edit menu, this script uses the metadata stored in CG .EXRs to extract an animated camera. You can run it when you have a read node selected.

[![Nuke15.0_osisoeFpqn.png](https://docs.vfxim.nl/uploads/images/gallery/2024-10/scaled-1680-/nuke15-0-osisoefpqn.png)](https://docs.vfxim.nl/uploads/images/gallery/2024-10/nuke15-0-osisoefpqn.png)

#### Breakout .PSD to 3d cards - By Mervin van Brakel

This tool was made specifically for concept artists who want to use Nuke to bring some 3d perspective to their 2d Photoshop layers. You can run it from the Edit menu when you have a read node selected which points to a Photoshop file. It will take your Photoshop layers and lay them out into the Nuke 3d scene.

[![Nuke15.0_Sbo4fcyPsA.png](https://docs.vfxim.nl/uploads/images/gallery/2024-10/scaled-1680-/nuke15-0-sbo4fcypsa.png)](https://docs.vfxim.nl/uploads/images/gallery/2024-10/nuke15-0-sbo4fcypsa.png)

#### PySide\_Compat by Robbert Scholten

In 2026 we switched our supported Nuke versions from Nuke 15 to Nuke 16 &amp; 17. One of the most impactful changes between those versions was Foundry's switch from PySide2 to PySide6.  
PySide is a UI library used in a lot of Nuke plugins that are part of our pipeline. The switch from PySide2 to PySide6 came with some big changes; modules were renamed and restructured, some classes moved between modules, and a number of methods were renamed or removed entirely

Porting all our scripts to PySide6 by hand would have been lots of work, and would have left older Nuke versions broken.  
Inspired by shims like Qt.py we came up with a different solution: **pyside\_compat.py**

The result is that all our existing scripts stay almost entirely untouched. The only change needed is the import statement at the top of each file. Instead of importing PySide2 (or PySide6) directly, scripts now import from pyside\_compat.

When pyside\_compat is imported, it figures out which PySide is available in the user's Nuke version by trying to import PySide2 first, and falling back to PySide6:  
On older Nuke versions (Nuke 15 and earlier), PySide2 works, so pyside\_compat simply sends back the real PySide2 modules. Everything behaves exactly as it always did.  
On newer Nuke versions (Nuke 16+), PySide2 isn't available, so it imports PySide6 instead, and applies some patches on top. These patches re-add the renamed/moved/removed APIs so that our PySide2-style code keeps working. Pyside\_compat acts as a dictionary: our scripts are still written in PySide2, but compat makes sure PySide6 can read/understand them.

This way we can keep all our scripts unmodified across every Nuke version we support, instead of maintaining two PySide2 and PySide6 branches.

**When adding new tools to our pipeline, please try to change any PySide import lines to pyside\_compat. Especially for older PySide2 scripts, this makes sure everything will work across all our supported Nuke versions.**

```
EXAMPLE:

# Before
from PySide2 import QtCore, QtGui, QtWidgets
from PySide2.QtCore import Qt

# After
from pyside_compat import QtCore, QtGui, QtWidgets, Qt
```


#### Additional custom tools

Tools under the BreakTools, MagicTools and MaximumFX tabs were also all made by students!

[![Nuke15.0_RrhZuLHVde.png](https://docs.vfxim.nl/uploads/images/gallery/2024-10/scaled-1680-/nuke15-0-rrhzulhvde.png)](https://docs.vfxim.nl/uploads/images/gallery/2024-10/nuke15-0-rrhzulhvde.png)