Advanced Link Logic
In the previous chapters, we discovered the power of Links in your composition. We also discovered that link targets are used a lot in Smode (in cues, exposed parameters, local links and links with hardware devices).
Since the targets can always contain Link Modifiers and Link Conditions, what you'll learn in this topic applies to a lot of scenarios.
Through that, you can add logic to a simple variable binding. You can remap the value of a real-world fader to something that has meaning in your composition. You can do a lot of things. Let's learn how to do some of them.
CREATE A LINK MODIFIER
Link modifiers can be created on a Link, a Parameter or a Target (the element inside a Link, a Parameter or a Cue). You can do that by right-clicking it and using the Modifier menu.
That topic is in the process of being updated. Everything might not match the latest version of Smode.
Each Actions have an input and an output value.
The input value of an Action is the output value of the preceding Action, or the Source value if there is no preceeding Actions.
The output value of an Action is the input value of the next Action, or the Target parameter if there is no further Actions.
So the Actions ordering is very important and must be chosen carefully.
Actions are divided in four categories:
- The Condition Actions, which can filter the parameters binding.
- The Modifier Actions, which perform arithmetical modification of the input value before sending it to its output.
- The Converter Actions, which allow to perform complex type conversion between input and output.
- The Dynamic Actions, which perform time based arithmetical modification of the input Value before sending it to its output.
The Source value reaches the target parameters only if all Condition Action are verified.
If no Converter Action is used, the Action input type is the type of the Action owner:
- Action owned by Rule uses the Source value type.
- Action owned by Variable uses the Variable value type.
- Action owned by Target uses the parameter type.
All Actions do not work with any type.
Rule can have Source and Target of different types.
If Converter Action is not available, the Action owner should be chosen carefully depending on the compatibility type.