Mappings will allow you to create a continuous relationship between a module's value and the parameter of a command, like "The volume of my voice will be continuously controlling the opacity of a video"
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-M0J7AAdUHj1EneIvO7J%252Fmapping.gif%3Fgeneration%3D1581959439265788%26alt%3Dmedia&width=768&dpr=4&quality=100&sign=3a8ba4061897e8ebfc57f27fd9537741e6891f5056697b5a5f33c77c546fb3fe
You can here choose the input value you want as a source to control your commands parameters.
You can use multiple input values to process them together or do operation between them.
The lighting symbol toggles whether a change in the input value triggers the mapping. This is helpful if you have multiple inputs and only want the mapping to trigger when a specific input changes.
To fill
If you want to modify the input value before sending to to the commands, you can add filters to change the value. In the example above, i choose to inverse the input value before sending it to the output section. You can check all filters there :
<aside> 💡 If you have multiple inputs, you can select which one a filter will process using the “Channels” menu in the filter header.
</aside>
Outputs are the commands you want to send each time the value has changed. Commands will automatically lock one of their parameter to the output value of this mapping, but you can change and select which output value to link with which parameter.