X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fosc58-querying-ardour.html;h=6ab925e0b675e1c8104753e01a1671f3354ecb20;hb=75b4514f778d6b1e3af9ed9739f731676330d454;hp=fed62f370f8b9bef6bb9202def3a99846339e694;hpb=7be4f507991a0b87174a0e78831a4e7e9e96bcbe;p=ardour-manual diff --git a/include/osc58-querying-ardour.html b/include/osc58-querying-ardour.html index fed62f3..6ab925e 100644 --- a/include/osc58-querying-ardour.html +++ b/include/osc58-querying-ardour.html @@ -32,14 +32,22 @@ current session has. Ardour replies with a message for each strip with the following information: After all the strip messages have been sent, one final message is sent with: @@ -47,8 +55,16 @@
  • The text end_route_list
  • The session frame rate
  • The last frame number of the session
  • +
  • Monitor section present
  • +

    + 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 it's 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.