Actions are "one-time" conditionnal triggers. You will want to use them if you have an "if-then" scenario, like "If the volume of the microphone is more than 50%, then launch a video in Resolume"

https://bkuperberg.gitbook.io/~gitbook/image?url=https%3A%2F%2F654853773-files.gitbook.io%2F~%2Ffiles%2Fv0%2Fb%2Fgitbook-legacy-files%2Fo%2Fassets%252F-M0J6klA7kDd2pwFQXYj%252F-M0J77Q7DvhqgPT4biK8%252F-M0J7KX-AGnKQoj_HdTp%252Faction.gif%3Fgeneration%3D1581959448208198%26alt%3Dmedia&width=768&dpr=4&quality=100&sign=0b01d2146f3c99dde734fa0608e33181bf3884f67e2e5e0ea7989493cceae3b5

Conditions

Conditions are the "if" part of your action. You can have multiple conditions running together. Each time the conditions get validated, the action will be triggered.

There are 5 types of conditions : From Input Value, Scripts, Group, On Activate and On Deactivate

• The "From Input Value" is the most used one. It will let you compare a module's input value in different ways and decide whether the condition is validated or not.
• The Script conditions allows you to write complex conditions using scripts. You can find more about that in the Script Conditions section.
• The Group condition allows you to create nested groups of conditions to create more complex condition combinations, like "If I sing a D AND press this button, OR if I sing a G AND I press this other button"
• The onActivate and onDeactivate conditions are triggered when the state containing them gets activated or deactivated (not enabled / disabled). This can be used for two scenarios :
  • If you want to trigger some actions whenever this state gets activated, which is a good tool when using state transitions, then you can use this to ensure that you send all commands when entering in a different state of your project.
  • Because onActivate conditions get triggered when loading a project if the containing state is active, it can be used as a startup initialization action.

Each time a condition is validated, it will turned green. It will turn back to grey once it gets invalidated.

Consequences

Consequences are the "then" part of your action.

• Each time an action is validated, it will trigger all the commands contained in the "Consequences : TRUE" section.
• Each time an action is invalidated, it will trigger all the commands contained in the "Consequence : FALSE" section.

For each action, you can create as many consequences as you want, and it will trigger them all at once, allowing for synchronized control of different modules.

You have also options to delay the trigger after the action is validated, as well as staggering the trigger of each consequences, resulting in a regularly timed triggering of each consequence.