DaVinci Resolve Fusion Macros: Tool vs. Group Operator Explained

Davinci Fusion Macro Guide

How to Save Nodes in DaVinci Resolve as a tool or as a group

Are you tired of rebuilding the same node trees in DaVinci Resolve Fusion over and over again? 😫 We've all been there. You create a stunning effect, a perfect lower third, or a complex color grade, and then... you have to build it from scratch for the next project.

Enter the Fusion Macro! πŸ§™β€β™‚οΈβœ¨ It's not just a template; it's a powerhouse workflow accelerator that saves a group of nodes as a single, reusable tool.

Group Macro Vs Tool Macro result and location

But did you know there are actually two distinct types of macros that behave very differently under the hood? Let's dive deep into the world of .setting files and uncover the secrets of MacroOperator vs. GroupOperator. πŸ•΅οΈβ€β™€οΈπŸ’»


πŸ“‚ The Magic Extension: .setting

First things first: in the world of Blackmagic Design's DaVinci Resolve, macros are saved with the .setting extension. This simple text file holds the blueprint of your creativity.

You can open these files in any code editor like VS Code, Notepad++, or Sublime Text to peek at the matrix code behind your visual magic. πŸ€“πŸ“


βš”οΈ The Duel: Group Macro vs. Tool Macro

On the surface, they might look similar, but their behavior is worlds apart.

Difference of Group Macro and Tool Macro in Fusion

1. The "Group" Macro (Open Book) πŸ“–

Think of this as a transparent container. When you use a Group Macro, it appears as a single node, but you can double-click it to dive inside and see (or tweak) every single node and wire. It's fully editable and transparent.

2. The "Tool" Macro (Black Box) πŸ“¦

This is the true "Macro" experience. It behaves like a native Fusion tool. You see one single node, and you can only interact with the controls you specifically chose to expose. The internal structure is hidden, keeping your node graph clean and your secrets safe. πŸ”’


πŸ” The Code Reveal: Spotting the Difference

How do you tell them apart at a code level? It's simple! Open your .setting file in your favorite editor and look for the Tools object.

Group Macro & Tool Macro in VScode Screenshot

  • Tool Macro: Defined as MacroOperator. This tells Fusion, "Treat me as a single, solid tool."
  • Group Macro: Defined as GroupOperator. This tells Fusion, "I am a container of other tools."

Knowing this distinction gives you god-like power over your assets. You can even manually tweak a file to change its behavior if you know what you're doing! πŸ› οΈβš‘


🎨 How to Create Them in Fusion

Ready to build your own? Here is the step-by-step workflow to master both types.

  1. Select Your Nodes: Highlight the nodes in your flow that you want to bundle up. πŸ–±οΈ
  2. Right-Click: Bring up the context menu.
  3. Create Macro: Choose "Create Macro" to open the configuration window. βš™οΈ
  4. Pick Your Settings: Check the boxes for the parameters you want to expose to the user.
  5. Save the Magic:
    • For a Tool Macro (MacroOperator): Use the standard Save or Save As. This creates the single-node tool experience. Save as MacroOperator
    • For a Group Macro (GroupOperator): Group your nodes first (Ctrl + G), then right-click the Group and choose Settings > Save All As.... This preserves the group structure. Save as Group GroupOperator

🌟 Why This Matters?

Understanding the difference between MacroOperator and GroupOperator transforms you from a casual user to a Fusion Power User.

  • Use Group Macros when you need flexibility and might need to tweak the internal logic later.
  • Use Tool Macros when you want to distribute polished tools to other editors or sell them as assets, ensuring a clean, unbreakable user experience. πŸ’ΌπŸš€

Start organizing your chaotic node graphs today! Your future self will thank you. πŸ™β³

Related posts