Skip to content

Output Defaults Override

A reusable, named bundle of output settings — the same fields as Output Defaults (path, format, filename tokens, render mode, frame range, camera burst) — that any number of Scene nodes can opt into.

When to use it

Output Defaults applies to every Scene node in the graph, and there's only one per graph. When you need the same settings applied to some of your Scene nodes but not others — a different output path for hero shots vs. supporting shots, say — editing Output Defaults itself would affect everything, and editing each Scene node individually doesn't scale. An Output Defaults Override node sits in between: create as many as you need, give each one a name, and point any Scene node at whichever one applies to it.

The override ladder, from broadest to most specific:

Output Defaults  →  Output Defaults Override  →  Scene node  →  View Layer

Each tier only needs to set what's different from the one before it — anything left unset falls through to the next tier up.

Setting it up

  1. Add an Output Defaults Override node. Give it a name (shown at the top of the node) — this is just a label for the picker below, separate from the node's internal name.
  2. Configure whichever fields should differ from Output Defaults for the Scene nodes that will use this bundle.
  3. On each Scene node that should use it, enable Override Output Defaults (in the Output section) and pick this node from the list.

A Scene node can only use one Output Defaults Override at a time — there's no mixing fields from two different override bundles on the same Scene node.

Properties

Identical set of sections to Output Defaults: Output Path, Filename Tokens, Render Mode, Frame Range, and Camera Burst (when Render Mode is Camera Burst). See that page for what each field does.

Tips

  • Any number of these nodes can exist in one graph — unlike Output Defaults, which is limited to one.
  • A Scene node's own direct settings still win over whatever an Output Defaults Override provides, and the override node itself falls back to Output Defaults for anything it doesn't set — the same "fill only what's missing" behavior Output Defaults already uses for Scene nodes.
  • Useful for grouping Scene nodes by client, deliverable type, or shot category without touching the tree-wide Output Defaults.