diff --git a/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html index e74c7e7..f87c2f4 100644 --- a/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html +++ b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc.html @@ -93,39 +93,25 @@ here"/>

strip_types

- Strip Types are coming soon... check for more info sometime. For now - just use 0 (or anything else) as this is ignored. I don't know the bit - order just yet, but it will work similar to feedback below. Strip Types - will determine What kind of strips will be included in a bank. This would - include: Audio, MIDI, busses, VCAs, Master, Monitor and hopefully - hidden or selected strips. + strip_types is an integer made up of bits. The easy way to + 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, busses, VCAs, Master, Monitor + and hidden or selected strips.

+

Please see: + Calculating Feedback and Strip-types Values.

feedback

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.

- -

- So using a value of 17 would turn on feedback for strip and master - controls, but leave meters, timecode and bar/beat feedback off. -

+

Please see: + Calculating Feedback and Strip-types Values.

+

gainmode

Gainmode is a an int that acts as a bool: @@ -144,15 +130,15 @@ here"/>

Transport Control

-
/transport_stop
+
/transport_stop optional
-
/transport_play
+
/transport_play optional
/set_transport_speed s
where s is a float ranging from -8.0f to 8.0f
-
/ffwd
+
/ffwd optional
-
/rewind
+
/rewind optional
/goto_start
@@ -168,7 +154,7 @@ here"/>
where spos is the target position in samples and roll is a bool/integer defining whether you want transport to be kept rolling or not
-
/loop_toggle
+
/loop_toggle optional
@@ -189,7 +175,7 @@ here"/>
/toggle_punch_out
-
/rec_enable_toggle
+
/rec_enable_toggle optional
/toggle_all_rec_enables
(toggles all tracks' recording state)
@@ -226,15 +212,26 @@ here"/> Monitor, may be included in the list of SSIDs or not as set in /set_surface.

+

+ Some Surfaces (many Android applets) are not able to deal with more + than one parameter in a command. However, the two parameter commands + below can also be sent as /strip/command/ssid param. In this case the + param should be a float even if an int is required below. +

-
/bank_up
+
/bank_up
Change bank to the next higher bank.
-
/bank_down
+
/bank_down
Change bank to the next lower bank.
/strip/mute ssid mute_st
where mute_st is a bool/int representing the desired mute state of the track
/strip/solo ssid solo_st
where solo_st is a bool/int representing the desired solo state of the track
+
/strip/monitor_input ssid monitor_st
+
where monitor_st is a bool/int where 1 is forced input monitoring.
+
/strip/monitor_disk ssid monitor_st
+
where monitor_st is a bool/int where 1 is forced disk monitoring. When input and disk are both off, + Auto monitoring is enabled.
/strip/recenable ssid rec_st
where rec_st is a bool/int representing the desired rec state of the track
/strip/gain ssid gain
diff --git a/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc/02_feedback-in-osc.html b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc/02_feedback-in-osc.html index 84445e0..f2c9437 100644 --- a/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc/02_feedback-in-osc.html +++ b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc/02_feedback-in-osc.html @@ -56,8 +56,8 @@ title: OSC Feedback With Ardour
/rewind state
- +
/loop_toggle state
+
@@ -68,7 +68,9 @@ title: OSC Feedback With Ardour
/toggle_punch_out
/rec_enable_toggle state
-
+
Master record enabled.
+
/record_tally state
+
Some record enable is true or "ready to record"

Master and monitor strips

@@ -97,6 +99,16 @@ title: OSC Feedback With Ardour

For each of the following, ssid is the surface strip ID for the track

+

+ Some Surfaces (many Android applets) are not able to deal with more + than one parameter in a command. However, the two parameter commands + below can also be sent as /strip/command/ssid param. Feedback can be + set to match this with the /set_surface/feedback state + command. See + Calculating Feedback and Strip-types Values. +

+
/strip/name ssid track_name
where track_name is a string representing the name of the track @@ -105,6 +117,11 @@ title: OSC Feedback With Ardour
where mute_st is a bool/int representing the actual mute state of the track
/strip/solo ssid solo_st
where solo_st is a bool/int representing the actual solo state of the track
+
/strip/monitor_input ssid monitor_st
+
where monitor_st is a bool/int. True/1 meaning the track is force to monitor input
+
/strip/monitor_disk ssid monitor_st
+
where monitor_st is a bool/int. True/1 meaning the track is force to monitor disk, + where both disk and input are false/0, auto monitoring is used.
/strip/recenable ssid rec_st
where rec_st is a bool/int representing the actual rec state of the track
/strip/gain ssid gain
diff --git a/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc/03_calculating-feedback-and-strip-types-values.html b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc/03_calculating-feedback-and-strip-types-values.html new file mode 100644 index 0000000..4050576 --- /dev/null +++ b/_manual/22_using-control-surfaces/01_controlling-ardour-with-osc/03_calculating-feedback-and-strip-types-values.html @@ -0,0 +1,101 @@ +--- +layout: default +title: Calculating Feedback and Strip-types Values +--- + +

/set_surface has two values the user needs to calculate before + use. In general these will not be calculated at run time, but + beforehand. There may be more than one button with different values + to turn various kinds of feedback on or off or to determine which + kinds of strips are currently viewed/controlled. +

+

Both ,feedback and strip-types use bitsets to keep + track what they are doing. Any number in a computer is made out of + bits that are on or off, but we represtent them as normal base 10 + numbers. Any one bit turned on will add a unique value to the + number as a whole. So for each kind of feedback or strip type + to be used, that number should be added to the total.

+

strip_types

+

+ strip_types is an integer made up of bits. The easy way to + 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, busses, VCAs, Master, Monitor + and hidden or selected strips. +

+ +

+ 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. +

+ +

feedback

+

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. +

+ +

+ So using a value of 19 would turn on feedback for strip and master + controls, but leave meters, timecode and bar/beat feedback off. +