ardour/manual
13
0
Fork 0
Code Pull Requests Releases Activity

OSC added some ids to take reader directly to relevant info

Browse Source
This commit is contained in:
Len Ovens 2017-11-10 17:34:25 -08:00
parent c74044cf79
commit f56f685d73
3 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
include/osc58-controlling-ardour-with-osc.html
View File

@ -158,7 +158,7 @@ here</em>"/&gt;</kbd>
then adding all those numbers together for a value to send.
</p>
<p>Please see: <a
href="@@osc58-feedback-and-strip-types-values">
href="@@osc58-feedback-and-strip-types-values#feedback">
Calculating Feedback and Strip-types Values.</a></p>
<p class="note">
Feedback can also be set with <em>/set_surface/feedback feedback.</em>

26
include/osc58-feedback-and-strip-types-values.html
View File

@ -62,22 +62,22 @@
Hidden strips. Using Hidden with other flags will allow Hidden strips
to show inline with other strips.
</p>
<h3 id="use-group">Use Group</h3>
<p class="note">
<p class="note" id="use-group">
Use Group on will tell ardour that any control on a strip that is part
of a group will affect all strips within that group. Default is off
or the control should only affect the strip the control is applied to.
The <code>/use_group f state</code> command can be used to temporarily
change this on the fly.
<p>
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
just a bank of fader strips, adding master or monitor would allow
access to them within the banks. Selected would be useful for working
on a group or a set of user selected strips. Hidden shows strips the
GUI has hidden.
Some handy numbers to use might be: 15 (all tracks and busses -
1 + 2 + 4 + 8), 31
(add VCAs to that - 15 + 16). 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 just a bank of fader strips, adding master or monitor
would allow access to them within the banks. Selected would be useful
for working on a group or a set of user selected strips. Hidden shows
strips the GUI has hidden.
</p>
<p class-"note">
Audio Aux? say what? I am sure most people will have noticed that they
@ -95,7 +95,7 @@
to enable both busses and auxes if they would prefer.
</p>
<h2>feedback</h2>
<h2 id="feedback">feedback</h2>
<p>Feedback is an integer made up of bits. The easy way to
deal with this is to think of feedback items being worth a number and
then adding all those numbers together for a value to send.
@ -147,7 +147,7 @@
</li>
</ul>
<p>
So using a value of 19 would turn on feedback for strip and master
controls, but leave meters, timecode and bar/beat feedback off.
So using a value of 19 (1 + 2 + 16) would turn on feedback for strip
and master controls, but leave meters, timecode and bar/beat feedback off.
</p>

4
include/osc58-feedback.html
View File

@ -69,7 +69,7 @@
<p>
These messages are feedback only. They are sent as status from Ardour
and some of them may be enabled separately from other feedback. See:
<a href="@@osc58-feedback-and-strip-types-values">
<a href="@@osc58-feedback-and-strip-types-values#feedback">
Calculating Feedback and Strip-types Values.</a>
</p>
<p class="note">
@ -174,7 +174,7 @@
below can also be sent as /strip/command/ssid param. Feedback can be
set to match this with the /set_surface/feedback <em>state</em>
command. See <a
href="@@osc58-feedback-and-strip-types-values">
href="@@osc58-feedback-and-strip-types-values#feedback">
Calculating Feedback and Strip-types Values.</a>
</p>