|
Parameter AutomationIn principle, all parameters of Reverb.it can be
automated, provided that your VST host software is capable of parameter automation (please see your VST host’s documentation for this issue). However, some of the parameters should only be changed while output is muted
and for some parameters we do not recommend automation at all. Here is a table of parameters and their suitability:
Suitable for automation: |
DECAY, DENSITY, LOW SHELF CENTER, LOW SHELF GAIN, HIGH SHELF CENTER, HIGH SHELF GAIN, MIX, OUTPUT, LOW DAMPING DECAY, HIGH DAMPING
DECAY,LOW DAMPING XOVER, HIGH DAMPING XOVER |
Automate while output is muted: |
PREDELAY |
Don’t automate: |
LOW DAMPING SWITCH, HIGH DAMPING SWITCH, QUALITY |
Parameters in the second category should only be automated when the output is muted since they produce audible artefacts when
modified (you need to mute outside the plugin since the output knob only reduces gain by at most -24 dB).Parameters in the third category should not be automated at all since
they change the CPU usage of the plugin (for example, switching on both LOW DAMPING and HIGH DAMPING at the same time nearly triples the number of required CPU cycles) and heavy changes of CPU usage
can result in dropouts or jitter during online audio processing. On the other hand, if you do offline processing then automating these parameters while the output is muted is perfectly fine. MIDI Automation
Reverb.it is not able to recieve MIDI data directly. Hence, automation of parameters by MIDI data is only possible if your host software is capable of assigning MIDI controller data to plugin parameters. |
|