Search Tips

Search is based on keyword.

`Ex: "Procedures"`

Do not search with natural language

`Ex: "How do I write a new procedure?"`

Give Feedback Support Portal

# Adding Burn-in Text to Exports

Hiero can burn-in text during the export process using a simple Nuke gizmo. The gizmo is accessed from the Nuke Write Node preset's Content panel under Burn-in.

The gizmo contains controls for the font style and fields denoting the position of the text. You can also add burn-in directly on timeline using the Burn-In soft effect. See Adding Effects on the Timeline for more information.

Note: The Font field only accepts the full file path and name of the font file to use. For example, on Mac ~/Library/Fonts/Verdana.ttf

Click Edit to display the available controls.

You can mix-and-match the following methods to create burn-in text:

• Enter text manually, what you see is what you get in the burn-in.

• Use any of the tokens valid in the shot template as burn-in tokens. For example:

{shot}_comp

Extracts the shot nam from the timeline and appends _comp.

See Using Local and Project Presets for more information.

• Use metadata from tags applied to clips and shots. For example:

[metadata hiero/shot/tags/Approved]

Extracts the Approved tag from the clip or shot. You can also append note to include any notes associated with the tag:

[metadata hiero/shot/tags/Approved/note]

Note: You must precede spaces and slashes in the tag name with \\ (backslashes) to enable Hiero to process the tag name correctly. For example: [metadata hiero/shot/tags/Blue\\ Screen/note]

Tip: If you're not sure what metadata keys and values are available on a shot, you can add a Text soft effect containing the Tcl expression [metadata values] to display all metadata in the Viewer. See Adding Effects on the Timeline for more information.

Did you find this helpful?

Yes No

## Sorry you didn't find this helpful

Why wasn't this helpful? (check all that apply)

Couldn't find what I was looking for
Instructions are confusing
Instructions didn't work
Title is misleading
Content is out-of-date
The translation is poor

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.

That's great!

Thanks for taking time to give us feedback.