Blackmagic Forum

While trying to figure out why some of the v19 fusion effects that I have installed are not working when I drag them onto the timeline in v20 beta 2, I found a reproducible fix. Might help others diagnose similar issues, and perhaps BMD can change v20 to handle the issue.

When the effect clip was dragged onto the timeline (in this case, an animated callout), the image went black. Entering Fusion on the callout clip showed the node tree was failing to generate an image.

After much digging around, I found that one node had a single user control that had "None" set for the Input Ctrl type. Changing None to any other value (Sliding Ctrl) - makes the whole node tree work (in addition to making the control visible on the User tab of the Inspector panel for the node).

Indeed DR v20 will not even let me change the setting back to None - it quietly keeps the previous Sliding setting if I change Input Ctrl to None, close the Input panel, and reopen the Input panel to check it again.

The behavior is consistent. In the attached zip, the file "callout_fails.txt" is a copy/paste of the grouped effect used with v19 and can be pasted into a Fusion composition. The file "callout_works.txt" is the same effect except for the addition of the AnimValue input control definition around line 1783.

The original (equivalent) .setting file was located in ...\Blackmagic Design\DaVinci Resolve\Support\Fusion\Templates\Edit\Titles (on Windows).

I'm not sure why an earlier DR version created the .setting file without the control visible, but I think it would be helpful for DR20 to more gracefully handle such existing situations (if Input Ctrl has to be non-None, then set it to some default value when an effect is read).

Davinci Resolve Studio v20 beta 2.

Sounds reasonable and easy and I hope they address it!

The issue with that macro was that the AnimValue control hadn't been created properly at all. Your diff shows AnimValue being added - previously it did not exist in the UserControls table at all. When you changed it in the Edit Controls dialog, that created it properly, and then the macro started working. I'm surprised it ever worked, even in v19.

There were a couple other incorrectly-set values too, but they were less consequential. I'm guessing the author hand-edited it, but made some boo-boos. Attached is a fixed version.

You're right about the issue with setting the Input Control type to None. While it does actually set the tool's internals correctly, it doesn't properly update the current tool - if you cut & paste it, then it looks as expected. Alternatively, you can click the Hide button instead, that does the same thing.

Thank you for the updated .setting; I've installed that as replacement.