3 Ardour has automation modes for many of its controls. As of version
4 5.9, OSC can control what automation mode a fader uses.
5 (<a href="@@automation">See Automation.</a>)
8 The form of the automation mode command is:
11 <code>/strip/[control]/automation ii ssid mode</code>
15 <li>/strip may also be /select in which case the only parameter is the mode.</li>
16 <li>[control] as of Ardour version 5.9 control can be:
21 This list will expand.
23 <li>ssid can be a parameter as shown or inline (automation/[ssid]). /select has no ssid.</li>
24 <li>mode can be one of:
26 <li><code>0</code> Manual mode</li>
27 <li><code>1</code> Play mode</li>
28 <li><code>2</code> Write mode</li>
29 <li><code>3</code> Touch mode</li>
31 The mode value may be sent as a float allowing a "pot" or "slider" with a range of
32 0 to 3 to be used to control mode.
37 The next version of Ardour will add <code>/strip/[control]/automation_name is ssid mode_name</code>
38 as feedback. A surface may choose to use only the first character of the string (M, P, W or T) instead of
39 the whole string (this is in git now).
42 The touch mode needs more input so there is a Touch command as well (added post 5.9). It is almost identical
43 to the automation command:
46 <code>/strip/[control]/touch ii ssid touch</code>
49 The only difference is the last parameter is 1 for touched and 0 for touch released. All of the rest
50 of the explanation above applies.