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.

Support for the following:

• Apple ProRes 4444 XQ 12-bit

• Apple ProRes 4444 12-bit

• Apple ProRes 422 HQ 10-bit

• Apple ProRes 422 10-bit

• Apple ProRes 422 LT 10-bit

• Apple ProRes 422 Proxy 10-bit

Alexa Mini LF

Codex HDE

On Windows, the AVI reader uses 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 is unable to open the .avi file.

Includes RAW 2.5K CinemaDNG

YCbCr encoded DPX files are not supported on the timeline.

To use DTEX files, you need Pixar’s PhotoRealistic RenderMan® Pro Server 20, or earlier, on your computer.

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.

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.

The writer supports the following codecs:

• Animation

• Apple ProRes 4444 XQ 12-bit

• Apple ProRes 4444 12-bit

• Apple ProRes 422 HQ 10-bit

• Apple ProRes 422 10-bit

• Apple ProRes 422 LT 10-bit

• Apple ProRes 422 Proxy 10-bit

• Avid DNxHD 444 10-bit 440Mbit

• Avid DNxHD 422 10-bit 220Mbit

• Avid DNxHD 422 8-bit 220Mbit

• Avid DNxHD 422 8-bit 145Mbit

• Avid DNxHD 422 8-bit 36Mbit

Note:  Interlaced writing is not supported. See Avid DNxHD Notes for more information.

• H.264 Main 4:2:0 8-bit

• H.264 High 4:2:0 8-bit

• Motion JPEG A

• Motion JPEG B

• MPEG-4

• Photo - JPEG

• PNG

• Uncompressed

Note:  The mov32Reader and Writer has been removed for macOS Catalina (10.15) and deprecated under Windows, Linux, and macOS Mojave (10.14). The mov32: prefix is still currently available on deprecated OS, but unsupported. We recommend using the standard Nuke Read/Write controls, as mov32 is scheduled for removal in a future release.

Supported codecs include:

• Uncompressed 4:2:2 YCbCr 8-/10-bit

• Uncompressed 4:4:4:4 RGBA 8-/10-bit

• Uncompressed Avid 4:2:2 YCbCr 8-/10-bit

• Uncompressed Avid 4:4:4:4 RGBA 8-/10-bit

• JPEG2000

• Avid DNxHD (1080p and 720p 1920x1080 and 1280x720, 4:4:4:4 and 4:2:2) 36, 115, 120, 145, 175, 185, 220, 220x
See Avid DNxHD Notes for more information.

• Avid DNxHR:

• 8-bit 4:2:2

DNxHR LB, DNxHR SQ, and DNxHR HQ

• 12-bit

DNxHR HQX 422 and DNxHR 444

• Sony Raw from the F65, F55, F5 and FS700 cameras. All formats that these cameras provide: 4K, 2K, 1K, 0.5K and 0.25K

• Sony X-OCN from the VENICE, F55, and F5 cameras.

• ARRIRAW from the Alexa Mini.

DNxHR Pattern: OP-1A, OP-Atom

Profiles:

• 4:4:4 12-bit

• HQX 4:2:2 12-bit

• HQ 4:2:2 8-bit

• SQ 4:2:2 8-bit

• LB 4:2:2 8-bit

Avid DNxHD Notes

The bit rates listed in the Codec Profile dropdown are the bit rates for 1080p at 29.97 fps EXCEPT for 36 fps (which is actually 45 Mbps @ 29.97fps). You should look at the codec format (422/444, 8/10-bit).

Note:  Nuke only supports 1080p and 720p. Non-HD resolutions are scaled to 1080p before writing.

This leads to a set of 1080p bit rates:

• 1080p/29.97 440x, 220x, 220, 145, 45

• 1080p/60 N/A, N/A, 440, 290, 90 (same at 59.94)

• 1080p/50 N/A, N/A, 367, 242, 75

• 1080p/25 365x, 185x, 185, 120, 36

• 1080p/24 350x, 175x, 175, 115, 36 (same at 23.976)

At 720p, the Codec Profile dropdown has a different interpretation. The bit rate is taken as the bit rate at 720p at 59.94fps. This leads to another set of bit rates:

• 720p/59.94 N/A, 220x, 220, 145, N/A

• 720p/50 N/A, 175x, 175, 115, N/A

• 720p/29.97 N/A, 110x, 110, 75, N/A

• 720p/25 N/A, 90x, 90, 60, N/A

• 720p/23.976 N/A, 90x, 90, 60, N/A

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 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

8 - DWAA compression, lossy DCT based compression, in blocks of 32 scan lines

9 - DWAB compression, lossy DCT based compression, in blocks of 256 scan lines

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.

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.

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.