

avi files, DirectShow tries to find the appropriate codec on the system. On Windows, in order to support more codecs, the AVI reader uses the DirectShow multimedia architecture. When working with Write nodes, you can also select mov64 from the file type dropdown menu and use avi as the file extension. If you get an error when using AVI files in Read nodes, you may need to use the prefix mov64: before the file path and file name, for example: Apple ProRes 422 includes the HQ, LT, and Proxy formats.ĪVI files can be supported by default or via Nuke’s reader/writer that is based on the FFmpeg open source library. To write meshes and point clouds out again, use the WriteGeo node.Īdds support for Apple ProRes 4444 and Apple ProRes 422 on Mac, Linux, and Windows using the mov64 reader.Īpple ProRes 4444 includes the SD, HD, 2K, UHD, and XQ formats. You can read meshes, point clouds, cameras, and transforms from Alembic files into a Nuke scene using the ReadGeo, Camera, and Axis nodes. The extensions listed under Extension let you specify the image format use these as the actual file name extensions or the prefix to indicate output format for the image sequences. The following table lists the supported file formats. To export deep images (in scanline OpenEXR format), use a DeepWrite node ( Deep > DeepWrite). To import deep images (either in DTEX or scanline OpenEXR format), use a DeepRead node ( Deep > DeepRead).To import lights from an FBX file, use the Light node ( 3D > Lights > Light). To import cameras or transforms from Alembic or FBX files, use the Camera node ( 3D > Camera).


To write them out again, use the WriteGeo node ( 3D > Geometry > WriteGeo). To import and export geometry objects from Alembic, FBX, or OBJ files, use the ReadGeo node ( 3D > Geometry > ReadGeo).When you render new images from Nuke ( Image > Write), you can use a file name extension to specify format.

