X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fosc58-querying-ardour.html;h=c94ec1009810981b6beec4a83cc4d69253bc033f;hb=c3904b1505337018b141b2b280f49d3158ba1ede;hp=20de95d449402823fa67d2c8b609a67d52b4c123;hpb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;p=ardour-manual diff --git a/include/osc58-querying-ardour.html b/include/osc58-querying-ardour.html index 20de95d..c94ec10 100644 --- a/include/osc58-querying-ardour.html +++ b/include/osc58-querying-ardour.html @@ -5,25 +5,29 @@ 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. Here are the commands used to query Ardour: (added in Ardour 5.5)
-/strip/list | +Ask for a list of strips |
---|---|
/strip/sends ssid | +Asks for a list of sends on the strip ssid |
/strip/receives ssid | +Asks for a list of tracks that have sends to the strip ssid points to |
/strip/plugin/list ssid | +Asks for a list of plug-ins for strip ssid. |
/strip/plugin/descriptor ssid piid | +Asks for a list of descriptors for plug-in piid on strip ssid |
/set_surface | +Ask for the current surface setting. Reply is in the same form as setting the surface would be. |
/surface/list | +Print a list of known surfaces and Link Sets to the log window. |
end_route_list
+ The /set_surface
should be set before this is called. That way
+ The right set of strips will be sent in return (though the default is good
+ for most uses) and feedback will start correctly.
+
+ If the surface is using /strip/list
, the surface needs to know
+ if the strips have changed. This would be true if a strip gets moved, created or
+ deleted. When this happens Ardour sends /strip/list
to the surfaces
+ that have previously requested a /strip/list
. This lets the
+ 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:
- /plugin/descriptor ssid piid
will
+ /strip/plugin/descriptor ssid piid
will
return the plug-in parameters for ppid plug-in on the ssid strip. The
- reply will contain the following information:
+ reply will be sent as a number of messages, one for each parameter.
+ Each message will contain the following information:
+ After all the parameters have been sent this way, one final message"
+ /strip/plugin/descriptor_end
is sent with these parameters:
+
The flag bitset above has been defined as (from lsb):
While this seems complex, it is really not that bad. Minimum, - maximum and value will in most cases give you all you need. + maximum and value will in most cases give you all you need. For simpler + access to plug-ins, the /select/plugin/ set of commands will handle most + needs. +
+
+ 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:
+
+