3 Ardour does not send every possible feedback value for each channel.
4 It does send expanded information on the selected channel. There are
5 also extra commands for the selected strip. All the feedback and
6 select commands have their own path <em>/select</em>.
7 This means that for the selected channel the surface does not have to
8 keep track of the strip ID. The /select strip will follow the
9 "current mixer strip" in the GUI editor window.
12 There are two major uses for this:
14 <li>Single strip control surfaces. Using
15 <em>/access_action Editor/select-next-route</em> or
16 <em>/access_action Editor/select-prev-route</em>
17 to step through the mixer strips.</li>
18 <li>Using a "Super strip" section of knobs to control parts
19 of the strip that are changed less often such as polarity, sends or
20 plugin parameters.</li>
24 Selection in Ardour's OSC implementation are complicated by the
25 possibility of using more than one OSC controller at the same time.
26 User "A" may select strip 4 and use a selected controller to make
27 changes to that strip. User "B" may subsequently select strip 7 to
28 make changes on. This leaves user "A" making changes to strip 7
29 which they did not choose.
32 For this reason Ardour offers local expansion aside from the GUI
33 selection. Local expansion only affects the one OSC controller. GUI
34 selection is global and affects all controllers using GUI selection
38 Both select and expansion use the /select set of commands.
41 In general, in a one user situation where that one user may use either
42 the OSC surface or the GUI, using GUI based selection makes the most
43 sense. This is the default because this is the more common use.
46 When there is more than one operator, then expansion only is the
47 mode of choice. It may make sense for one of the surfaces to
48 use GUI selection where the operator is also using the GUI for some
49 things. However, the set up should be carefully analyzed for the
50 possibility of selection confusions. Expansion should be
51 considered the <em>safe</em> option.
54 It is always OK to use expansion on the surface even in a one
55 user scenario. This allows the user to use GUI and surface selection
59 It is also possible to use both if desired. /strip/select will ways
60 set the GUI select, but /strip/expand will set the select feedback
61 and commands locally without changing the GUI select. Another
62 /strip/expand or a /strip/select will override that expand command
63 and releasing the /strip/expand or /select/expand (setting it to 0 or
64 false) will set the /select set of commands and feedback back to
65 whichever strip the GUI has selected at that time. This could be used
66 to switch between the GUI select and the local expand to compare two