You can read meshes, point clouds, cameras, and transforms from Alembic files into a Nuke scene using the ReadGeo, Camera, and Axis nodes.

To write meshes and point clouds out again, use the WriteGeo node.

AVI files can be supported by default or via Nuke’s reader/writer that is based on the FFmpeg open source library. If you get an error when using AVI files in Read nodes, you may need to use the prefix ffmpeg: before the file path and file name, for example, ffmpeg:\z:\job\FILM\IMG\final_comp_v01.####.avi. When working with Write nodes, you can also select ffmpeg from the file type dropdown menu and use avi as the file extension.

On Windows, in order to support more codecs, the AVI reader uses the DirectShow multimedia architecture. When decoding .avi files, DirectShow tries to find the appropriate codec on the system. If the codec is not available, DirectShow and Nuke are unable to open the .avi file. Note that the 64-bit version of Nuke can only use 64-bit DirectShow codecs. If you only have a 32-bit codec installed, the 64-bit version of Nuke cannot use it to open .avi files.

To use DTEX files, you need to set up Pixar’s PhotoRealistic RenderMan® Pro Server 15.2, 16.4, or 17.0 on your computer first.

To read a DTEX file, use the DeepRead node.

You can read meshes, point clouds, cameras, lights, and transforms from FBX files into a Nuke scene using the ReadGeo, Camera, Light, and Axis nodes.

To write geometry out again, use the WriteGeo node.

obsolete

This format stores an 8-bit mantissa for each of r, g, and b and an additional 8-bit exponent that is shared by all three, which packs the floating point RGB triplet into 32 bits per pixel.

Adjust compression levels using the quality slider in the Write node’s properties panel.

OpenEXR handles 16- and 32-bit float. This 16 is also called "half float" and is different from the 16-bit integer that all the other formats that support 16-bit use.

Nuke supports multi-part OpenEXR files. For more information, see Notes on Importing OpenEXR Files and Notes on Rendering OpenEXR Files.

When working with deep data, Nuke supports scanline OpenEXR files. For more information, see Importing Scanline OpenEXR Files and Writing Deep Data.

EXR Compression

EXR file metadata contains a compression key/value pair detailing the compression type used to write the .exr file. The value is expressed as the name of the compression type or an integer referencing the compression used:

0 - no compression

1 - RLE compression, run length encoding

2 - Zip compression, one scan line at a time

3 - Zip compression, in blocks of 16 scan lines

4 - PIZ-based wavelet compression, in blocks of 32 scan lines

5 - PXR24 compression, lossy 24-bit float

6 - B44 compression, lossy 4-by-4 pixel block, fixed rate

7 - B44A compression, lossy 4-by-4 pixel block, flat fields are compressed more

While Nuke reads standard Photoshop® blend modes, it doesn't read Photoshop layer comps or recognize group blend modes. Photoshop layers are read into separate Nuke layers and anything that doesn't map into that is ignored.

QuickTime is only supported by default on Windows and Mac OS X. To use QuickTime files on Linux, you need to use the prefix ffmpeg: before the file path and file name, for example,
ffmpeg:\z:\job\FILM\IMG\final_comp_v01.####.mov. When working with Write nodes, you can also select ffmpeg from the file type dropdown menu and use mov as the file extension. This way, Nuke will use its reader/writer that is based on the FFmpeg open source library to decode/encode QuickTime files.

DSLR raw data files, such as Canon .CR2 files. These are only supported via the dcraw command-line program, which you can download from the dcraw website. Bit depth and other specifications depend on the device. Some devices may not be supported.

Note that .r3d files may look different in Nuke compared to various versions of RED applications, like RED ALERT or REDCINE. Unlike most other file formats Nuke reads, the .r3d REDCODE files must be processed to convert from a raw format to an RGB color image. From time to time, a new version of the RED SDK that Nuke uses improves this processing and due to the timing of release cycles, Nuke may sometimes be using a different version than the RED applications.

If utilized, the compression schema on imported TIFF sequences must be LZW®.

This is the text-based format in which Nuke’s interface elements are stored.