Blackmagic Forum

I am still wondering if that is a bug or not: as soon as I publish a custom control (in this case a slider I created in the "User" section of a background node), it can't be animated. The context menu shows "Set key", but setting a key has no effect.

If I unpublish the control it can be animated again.

Can someone confirm this behaviour?

Fusion 9 free on Windows 7 64bit.

Best, Marin

I think this might be a case of user confusion. As soon as you publish a value this can no longer be animated. Publishing a value is used for non-animated values.
*all* animated values in Fusion are effectively published by default.

If I've recreated your steps correctly, then you will find the published slider availabe under 'modifiers' - this slider *can* be animated.

But this brings me back to the original question: why would you want to publish *and* animate?

I do agree with you that there shouldn't be an option to 'set key' if it doesn't do anything.
But the actual behaviour is consistent with the rest of Fusion.

User confusion indeed.

At first glance and without knowing too much about Fusion I thought that publishing a parameter enables it to drive any other parameter. Some hundred hours of training later it turns out (among many other things) that publishing makes a parameter visible to other controls so it can be driven by them.. I hope I got it right this time

Marin Goleminov wrote:User confusion indeed.

At first glance and without knowing too much about Fusion I thought that publishing a parameter enables it to drive any other parameter. Some hundred hours of training later it turns out (among many other things) that publishing makes a parameter visible to other controls so it can be driven by them.. I hope I got it right this time

I am not even sure what you mean by this question.

In Fusion when you animate a parameter its properties become automatically accessible to all other tools in the RC-menu. You can connect to them, modify them with calculations etc.
Publishing is - traditionally - used to make *static* values available to other tools as well, without having to resort to expressions etc. Once connected they act in a bidirectional way: changing it in one place changes it in the other. Does this help?

It wasn't a question ... but I'm glad You answered, because to all the other knowledge I can add the "bidirectional" manner of connected sliders