Search is based on keyword.
Do not search with natural language
Ex: "How do I write a new procedure?"
Writing Deep Data
You can write out deep images in the scanline OpenEXR 2.3, or above, format using the DeepWrite node, which shares a lot of controls with the standard Write node. Do the following:
|1.||Select Deep > DeepWrite to insert a DeepWrite node into your script.|
|2.||In the properties panel, click the file or proxy field’s folder icon and browse to the directory where you want to store the deep image.|
|3.||After the path, type a name for the deep image, including the .exr extension, and then click OK. If you’re rendering an image sequence, include the frame number variable (for example, ####) in the name.|
|4.||Use the datatype dropdown menu to select the bit depth for the rendered file: 16 bit half or 32 bit float.|
|5.||Set compression to the compression type to apply to the rendered file.|
|6.||From the metadata dropdown menu, select what metadata is included with the rendered file:|
• no metadata - No custom attributes are created, and only metadata that fills required header fields is written out.
• default metadata - The optional time code, edge code, frame rate, and exposure header fields are also filled using metadata values.
• default metadata and exr/*
• all metadata except input/*
• all metadata
|7.||By default, unknown metadata keys have the prefix nuke attached to them when they are written into the file. If you’d rather have them written into the file "as is", without the prefix, check do not attach prefix.|
|8.||Adjust the rest of the controls as necessary. For more information on them, see Output (Write) Nodes.|
|9.||Click the Render button.|
Nuke prompts for a frame range, defaulting to the range in the frame range fields.
|10.||If necessary, change the start and end frames, and then click OK.|
Nuke writes the deep data to a scanline OpenEXR 2.3, or above, file (tiled OpenEXR files are not supported).
Sorry you didn't find this helpful
Why wasn't this helpful? (check all that apply)
Thanks for your feedback.
If you can't find what you're looking for or you have a workflow question, please try Foundry Support.
If you have any thoughts on how we can improve our learning content, please email the Documentation team using the button below.
Thanks for taking time to give us feedback.