X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fautomation-states.html;h=4f779dd107961b52ef5c5b7e6eceedb163bbad51;hb=252cfd80174df0772747e8c2589014937cbed0e3;hp=69c17a56971cfd50b49e744f31954979c4480cce;hpb=7f3a2e0d56976433b23555fa6ff949107ebf1595;p=ardour-manual diff --git a/include/automation-states.html b/include/automation-states.html index 69c17a5..4f779dd 100644 --- a/include/automation-states.html +++ b/include/automation-states.html @@ -1,9 +1,12 @@

In order to understand how automation in Ardour works, it is necessary to - understand the four states of automation. They are: Manual, Play, Write, and Touch. + understand the five states of automation. They are: + Manual, + Play, + Write, + Touch, + and Latch.

@@ -36,13 +39,23 @@ control during playback; all such settings are written to the lane the control is in. This defines the lane's automation curve in the interval being played, and overwrites any existing automation curve in the lane being - manipulated. + manipulated. As this might be sometimes dangerous, this state is automatically + changed to Touch state when playing is stopped.

Touch state is similar to Write - mode, except it only overwrites sections of a lane's automation curve when + state, except it only overwrites sections of a lane's automation curve when the control is changed in some way. This allows for changing only the parts of an automation curve that are desired to be changed, while leaving the rest unchanged.

+ +

+ Latch state is similar to Touch + state as it will also change automation when the control is changed in some way + during session play back. + But additionally it will overwrite the automation curve with the last + value that it was changed to until play-back is stopped.
+ Latch state is also useful when the user wants Touch-style behavior but is using a device incapable of sending messages to indicate the start and end of the "touch". +