diff --git a/include/controlling-track-ordering.html b/include/controlling-track-ordering.html index 4a36b4b8..6a943cbc 100644 --- a/include/controlling-track-ordering.html +++ b/include/controlling-track-ordering.html @@ -81,7 +81,7 @@
- Remote IDs are assigned to tracks and buses in the order that they appear in + Remote IDs are assigned to tracks and busses in the order that they appear in the mixer window from left to right, starting from #1; manual assignment of remote IDs is not possible. The master bus and monitor section can be accessed by name. diff --git a/include/osc58-controlling-ardour-with-osc.html b/include/osc58-controlling-ardour-with-osc.html index daea2866..76d71536 100644 --- a/include/osc58-controlling-ardour-with-osc.html +++ b/include/osc58-controlling-ardour-with-osc.html @@ -110,13 +110,13 @@ here"/> deal with this is to think of strip_types items being worth a number and then adding all those numbers together for a value to send. Strip Types will determine what kind of strips will be included in - bank. This would include: Audio, MIDI, buses, VCAs, Master, Monitor + bank. This would include: Audio, MIDI, busses, VCAs, Master, Monitor and hidden or selected strips.
Aside from setting the track types for the main mix assignments, using /set_surface/strip_types with more than one surface button will allow - switching between modes for example: inputs only, buses only, + switching between modes for example: inputs only, busses only, selected only, hidden only, by having the buttons send values of: 3, 12, 256, 512. A full mix button might have a value 31.
diff --git a/include/osc58-feedback-and-strip-types-values.html b/include/osc58-feedback-and-strip-types-values.html index a77f196d..e19a4374 100644 --- a/include/osc58-feedback-and-strip-types-values.html +++ b/include/osc58-feedback-and-strip-types-values.html @@ -28,10 +28,10 @@ 2 - MidiTracks.- Some handy numbers to use might be: 15 (all tracks and buses), 31 + Some handy numbers to use might be: 15 (all tracks and busses), 31 (add VCAs to that). Master or Monitor strips are generally not useful on a surface that has dedicated controls for these strips as there are /master* and /monitor* commands already. However, on a surface with @@ -72,17 +72,17 @@
Audio Aux? say what? I am sure most people will have noticed that they can find no Aux strips in the Ardour mixer. There are none. - There are buses that can be used a number of ways. From analog days, + There are busses that can be used a number of ways. From analog days, in OSC, a bus is something that gets used as a sub mix before ending up going to Master. An auxiliary bus is used like a separate mixer and it's output goes outside the program or computer to be used as: a monitor mix, a back up recording, or what have you. In OSC where controller strips may be limited, it may be useful not to use up a strip for an aux that is not really a part of the mix. It is also - useful to get a list of only aux buses if the control surface is a + useful to get a list of only aux busses if the control surface is a phone used to provide talent monitor mix control on stage. Each performer would be able to mix their own monitor. The user is free - to enable both buses and auxes if they would prefer. + to enable both busses and auxes if they would prefer.