You are here: Reference Guide > Filter Nodes > MotionBlur

MotionBlur

MotionBlur (NukeX only) uses the same techniques and technology as the motion blur found in Kronos to add realistic motion blur to a sequence, but presents the controls in a less complex, more user friendly way.

Inputs and Controls

Connection Type	Connection Name	Function
Inputs	FgVecs	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. The BgVecs input only appears once you have connected all the other inputs.
	BgVecs
	Matte	An optional matte of the foreground, which may improve the motion estimation by reducing the dragging of pixels that can occur between foreground and background objects.
	Source	The sequence to receive the motion blur effect.

Control (UI)	Knob (Scripting)	Default Value	Function
MotionBlur Tab
Local GPU	gpuName	N/A	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 GPU 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 Device, if available, by navigating to the Preferences and selecting an alternative from the GPU Device dropdown. NOTE: Selecting a different GPU requires you to restart Nuke before the change takes effect.
Use GPU if available	useGPUIfAvailable	enabled	When enabled, rendering occurs on the Local GPU specified, if available, rather than the CPU. The output between the GPU and CPU is identical, but using the GPU can significantly improve processing performance. NOTE: Enabling this option with no local GPU allows the script to run on the GPU whenever the script is opened on a machine which does have a GPU available. You should also select this if you wish to render from the command line with the --gpu option. The GPU processing also requires certain NVIDIA GPUs and CUDA drivers. For more information on the minimum requirements, please refer to the Nuke Release Notes available in Help > Release Notes.
Shutter Samples	shutterSamples	3	Sets the number of in-between images used to create an output image during the shutter time. Increase this value for smoother motion blur.
Shutter Time	shutterTime	0.75	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.
Vector Detail	vectorDetail	0.2	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.
Matte Channel	matteChannel	None	Where to get the (optional) foreground mask to use for motion estimation: • None - do not use a matte. • Source Alpha - use the alpha of the Source input. • Source Inverted Alpha - use the inverted alpha of the Source input. • Matte Luminance - use the luminance of the Matte input. • Matte Inverted Luminance - use the inverted luminance of the Matte input. • Matte Alpha - use the alpha of the Matte input. • Matte Inverted Alpha - use the inverted alpha of the Matte input.