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