3 title: Calculating Feedback and Strip-types Values
6 <p><em>/set_surface</em> has two values the user needs to calculate before
7 use. In general these will not be calculated at run time, but
8 beforehand. There may be more than one button with different values
9 to turn various kinds of feedback on or off or to determine which
10 kinds of strips are currently viewed/controlled.
12 <p>Both ,<em>feedback</em> and <em>strip-types</em> use bitsets to keep
13 track what they are doing. Any number in a computer is made out of
14 bits that are on or off, but we represent them as normal base 10
15 numbers. Any one bit turned on will add a unique value to the
16 number as a whole. So for each kind of feedback or strip type
17 to be used, that number should be added to the total.</p>
20 strip_types is an integer made up of bits. The easy way to
21 deal with this is to think of strip_types items being worth a number and
22 then adding all those numbers together for a value to send.
23 Strip Types will determine What kind of strips will be included in
24 bank. This would include: Audio, MIDI, busses, VCAs, Master, Monitor
25 and hidden or selected strips.
60 Selected and Hidden bits are normally not needed as Ardour defaults to
61 showing Selected strips and not showing Hidden strips. The purpose of
62 these two flags is to allow showing only Selected strips or only
63 Hidden strips. Using Hidden with other flags will allow Hidden strips
64 to show inline with other strips.
67 Some handy numbers to use might be: 15 (all tracks and buses), 31
68 (add VCAs to that). Master or Monitor strips are generally not useful
69 on a surface that has dedicated controls for these strips as there are
70 /master* and /monitor* commands already. However, on a surface with
71 just a bank of fader strips, adding master or monitor would allow
72 access to them within the banks. Selected would be useful for working
73 on a group or a set of user selected strips. Hidden shows strips the
77 Audio Aux? say what? I am sure most people will have noticed that they
78 can find no <em>Aux</em> strips in the Ardour mixer. There are none.
79 There are buses that can be used a number of ways. From analog days,
80 in OSC a bus is something that gets used as a sub mix before ending up
81 going to Master. An auxiliary bus is used like a separate mixer and
82 it's output goes outside the program or computer to be used as:
83 a monitor mix, a back up recording, or what have you. In OSC where
84 controller strips may be limited, it may be useful not to use up a
85 strip for an aux that is not really a part of the mix. It is also
86 useful to get a list of only aux buses if the control surface is a
87 phone used to provide talent monitor mix control on stage. Each
88 performer would be able to mix their own monitor. The user is free
89 to enable both buses and auxes if they would prefer.
93 <p>Feedback is an integer made up of bits. The easy way to
94 deal with this is to think of feedback items being worth a number and
95 then adding all those numbers together for a value to send.
99 1 - Button status for strips.
102 2 - Variable control values for strips.
105 4 - Send SSID as path extension.
108 8 - heartbeat to surface.
111 16 - Enable master section feedback.
114 32 - Send Bar and Beat.
120 128 - Send meter as dB (-193 to +6) or 0 to 1 depending on gainmode
123 256 - Send meter a 16 bit value where each bit is a level
124 and all bits of lower level are on. For use in a LED strip. This
125 will not work if the above option is turned on.
128 512 - Send signal present, true if level is higher than -40dB
131 1024 - Send position in samples
134 2048 - Send position in time, hours, minutes, seconds and milliseconds
137 8192 - Turn on extra select channel feedback beyond what a /strip supports
141 So using a value of 19 would turn on feedback for strip and master
142 controls, but leave meters, timecode and bar/beat feedback off.