Support for custom file header metadata – Apple Shake 4 User Manual

Page 178

Advertising
background image

178

Chapter 5

Compatible File Formats and Image Resolutions

When yuvFormat is set to Auto, the resolution is automatically determined by the
resolution of the FileIn node. The selected resolution is the smallest possible to fit the
entire image. For example, if the image is smaller than NTSC, it is NTSC. If it is between
NTSC and PAL, it is PAL; otherwise it is HD. You can also manually select the resolution.
The script.videoResolution is no longer used for this purpose.

Note: The YUV file reader and writer supports Rec. 709 and Rec. 601-1 colorimetry
coefficients, used primarily in HD YCbCr (HD-SDI).

Support for Custom File Header Metadata

Internal support for blind data allows for the preservation of metadata from custom file
formats for facilities using special file translators.

If you design a file translator that places a file’s header metadata into Shake’s blind data
container, it will be passed down through the node tree. For example, if you read in an
image with custom metadata using such a file translator, process it with a series of
single input nodes, then render out the result into the same format with a FileOut node,
the blind header data is passed through the node tree and written to the resulting file.

If two images with metadata in the blind data container are combined in a node, such
as Over, Outside, or Multilayer, the data from the image connected to the node’s left-
most input (frequently labeled the foreground input knot) is propagated down the tree.

If, at some point in the node tree, you wish to assign the blind header data from one
image to another, use the Copy node. This can be useful if you have a complex node
tree that uses many layer nodes combining several images, yet you want the final file to
render out with specific header data taken from one of the FileIn nodes.

YUV FileIn parameters

YUV FileOut parameters

Advertising