If the motion in your input sequence has been estimated before (for example, using FurnaceCore’s F_VectorGenerator or third-party software), you can supply one or more vector sequences to MotionBlur to save processing time.

If you have separate vectors for the background and foreground, you should connect them to the appropriate inputs and supply the matte that was used to generate them to the Matte input. If you have a single set of vectors, you should connect it to the FgVecs input.

Note:  The BgVecs input only appears once you have connected all the other inputs.

Displays the GPU used for rendering when Use GPU if available is enabled. Local GPU displays Not available when:

• Use CPU is selected as the default blink device in the Preferences.

• no suitable GPU was found on your system.

• it was not possible to create a context for processing on the selected GPU, such as when there is not enough free memory available on the GPU.

You can select a different GPU, if available, by navigating to the Preferences and selecting an alternative from the default blink device dropdown.

Note:   Selecting a different GPU requires you to restart Nuke before the change takes effect.

When enabled, rendering occurs on the Local GPU specified, if available, rather than the CPU. The output between the GPU and CPU is identical on NVIDIA GPUs, but using the GPU can significantly improve processing performance.

Nuke supports AMD GPUs on late 2013 Mac Pro 6,1, mid 2015 Mac Pro 11,5, and and late 2016 MacBook Pro 13,3, running OS X 10.9.3 'Mavericks', or later. While, in some cases the bit-wise equality between GPU and CPU holds, for some operations there are limitations to the accuracy possible with this configuration.

Note:  Enabling this option with no local GPU allows the script to run on the GPU whenever the script is opened on a machine that does have a GPU available.
You should also select this if you wish to render from the command line with the --gpu option.

GPU processing also requires certain NVIDIA and AMD drivers. For more information on the minimum requirements, please refer to the Nuke Release Notes available in Help > Release Notes.

Sets the number of in-between images used to create an output image during the shutter time. Increase this value for smoother motion blur, but note that it takes much longer to render.

Sets the equivalent shutter time of the retimed sequence. For example, a shutter time of 0.5 is equivalent to a 180 degree mechanical shutter, so at 24 frames per second the exposure time will be 1/48th of a second.

Imagine a gray rectangle moving left to right horizontally across the screen. The figures below show how Shutter Time affects the retimed rectangle.

Sets the method of calculating motion estimation vectors:

• Local - uses local block matching to estimate motion vectors. This method is faster to process, but can lead to artifacts in the output.

• Regularized - uses semi-global motion estimation to produce more consistent vectors between regions.

Note:  Scripts loaded from previous versions of Nuke default to Local motion estimation for backward compatibility. Adding a new MotionBlur node to the Node Graph defaults the Method to Regularized motion estimation.

Varies the density of the vector field. The larger vector detail is, the greater the processing time, but the more detailed the vectors should be.

A value of 1 generates a vector at each pixel, whereas a value of 0.5 generates a vector at every other pixel.

Sets the type of resampling applied when retiming:

• Bilinear - the default filter. Faster to process, but can produce poor results at higher zoom levels. You can use Bilinear to preview a motion blur before using one of the other resampling types to produce your output.

• Lanczos4 and Lanczos6 - these filters are good for scaling down, and provide some image sharpening, but take longer to process.