Macro Editor

Once a Group or Macro is created, you often need to hide the internal parameters and expose only the controls that are useful to the end user. The Macro Editor lets you turn parameters on or off and rename them for the Inspector.

Example: a Light Wrap macro exposes a Blur slider renamed "Softness" (instead of its technical internal name).

• Page: the Fusion page (not the Edit page, but title macros can be saved so they show up in the Edit page).
• Access: right-click the node tree → Macro → [MacroName].

Controls Customization

Turn specific parameters on or off. Rename them for the user. All the internal complexity stays hidden.

Saving Options

Once you are done, the Close dialog offers three choices: Yes (save), No (discard), or Cancel (go back to editing).

Group / Macro support

Works with local Groups AND with Macros saved in the Effects Library. A consistent workflow.

Title macros can be saved in dedicated system folders so they show up in the Effects Library of the Edit page:

macOS

Library > Application Support > Blackmagic Design > DaVinci Resolve > Fusion > Templates > Edit > Titles

Windows

AppData > Roaming > Blackmagic Design > DaVinci Resolve > Support > Fusion > Templates > Edit > Titles

Once the macro is saved in this folder, it automatically shows up in the Edit page Effects Library, ready to be dragged onto the timeline.

• Simplifying complex setups - expose 3-5 key parameters on a macro that holds 50 nodes inside.
• Building user-friendly custom effects - rename technical parameters with friendly names (e.g. "Softness" instead of "Blur Size").
• Title templates for the Edit page - build title animations available from the Edit page, with a few exposed controls.
• Team library - create a suite of standard tools every artist on the team can use, with a consistent UI.
• Project preset / template - the key effects of the project exposed as macros = a fast workflow from shot to shot.

• Rename for the user's sake - the end user sees the exposed names, not the internal ones. Pick intuitive names.
• Hide the complexity - turn off every internal parameter the user does not need. Keep only the essentials.
• Keep the source Group - keep a copy of the source Group (not the macro) so you can easily change the internal implementation later.
• Save in Templates > Edit > Titles - for a title macro to show up in the Edit page, put it in the dedicated folder.
• Test the macro first - before you finalize it, test it on several cases to check that it works well in different contexts.
• Team versioning - store the macro .setting files in Git or on a shared server for collaboration and rollback.
• For truly pro macros, also consider a thumbnail / preview image in the Templates folder for the best UX.