X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fosc58-querying-ardour.html;h=c94ec1009810981b6beec4a83cc4d69253bc033f;hb=a26b49e5c69ac38d5465c62623994e8a81f1b6b3;hp=fa2a6f9dd02df26f167b86a44f392acdaf131f8c;hpb=10010543f30a3ead3055afc9007a2693135879cc;p=ardour-manual diff --git a/include/osc58-querying-ardour.html b/include/osc58-querying-ardour.html index fa2a6f9..c94ec10 100644 --- a/include/osc58-querying-ardour.html +++ b/include/osc58-querying-ardour.html @@ -5,7 +5,7 @@ information. These set of commands are for smarter control surfaces That have the logic to figure out what to do with the information. These are not of value for mapped controllers like touchOSC and - friends. The controller will need to send these queries to ardour + friends. The controller will need to send these queries to Ardour as often as it needs this information. It may well make sense to use regular feedback for things that need to be updated often such as position or metering. @@ -25,6 +25,8 @@
/strip/list
to the surfaces
that have previously requested a /strip/list
. This lets the
- surface know that it's list of strips is no longer valid.
+ surface know that its list of strips is no longer valid.
A bus will not have a record enable and so a bus message will have one less parameter than a track. It is the controllers - responsability to deal with this. + responsibility to deal with this.
/strip/receives ssid
will return a list of
tracks that have sends to the bus at the ssid. The reply will
- contain the following information for each track conntected to this
+ contain the following information for each track connected to this
bus:
/strip/plugin/descriptor_end
is sent with these parameters:
+ Ardour can work with more than one OSC control surface at a time.
+ Sometimes it is useful to know the information stored about all
+ surfaces. Sending /surface/list
from any surface or selecting:
+ Print surface information to Log window from
+ the Debug dropdown in the OSC setup dialog,
+ will list all the information Ardour uses to calculate the feedback
+ it sends. The Log window can be opened from the menu with
+ Window > Log.
+ This would be useful information to include with any OSC
+ related Bug report. The output is printed in this format:
+
+ +