X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fosc58-feedback-and-strip-types-values.html;h=f1a44555b1aa824356ef33cb089203788365f9bf;hb=8fe36b823d4f931fc7a69526f4d1d8c14baef59b;hp=f64ad7f3acbd9945074e7993529d2c74f89a5f2e;hpb=042723be8949fe53bb488183a91e27c398d40ce4;p=ardour-manual diff --git a/include/osc58-feedback-and-strip-types-values.html b/include/osc58-feedback-and-strip-types-values.html index f64ad7f..f1a4455 100644 --- a/include/osc58-feedback-and-strip-types-values.html +++ b/include/osc58-feedback-and-strip-types-values.html @@ -43,7 +43,7 @@ 64: Monitor.
  • - 128: Audio Aux. + 128: FoldbackBusses.
  • 256: Selected. @@ -68,6 +68,7 @@ or the control should only affect the strip the control is applied to. The /use_group f state command can be used to temporarily change this on the fly. +

    Some handy numbers to use might be: 15 (all tracks and busses - 1 + 2 + 4 + 8), 31 @@ -77,24 +78,71 @@ 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. + strips the GUI has hidden. As such, a control surface will likely have + a number of buttons with different strip_types for convenience. +

    -

    - Audio Aux? say what? I am sure most people will have noticed that they - can find no Aux strips in the Ardour mixer. There are none. - There are busses that can be used a number of ways. From analog days, - in OSC, a bus is something that gets used as a sub mix before ending up - going to Master. An auxiliary bus is used like a separate mixer and - its output goes outside the program or computer to be used as: - a monitor mix, a back up recording, or what have you. In OSC where - controller strips may be limited, it may be useful not to use up a - strip for an aux that is not really a part of the mix. It is also - useful to get a list of only aux busses if the control surface is a - phone used to provide talent monitor mix control on stage. Each - performer would be able to mix their own monitor. The user is free - to enable both busses and auxes if they would prefer. +

    Using hidden strips

    +

    + Ardour allows any of it's strips to be hidden so that they do not show + up on the GUI mixer or editor. OSC follows the GUI by default and will + not show hidden strips. As of Ardour 6.0 the OSC commands include + /select/hide y/n for the selected + strip and /strip/hide ssid y/n + for any strip. This allows the control surface to hide or unhide a strip. + What may not be obvious is that hiding a strip makes it disappear and + become unselected. So if a selected strip is hidden, it is no longer + selected and the select channel will show the default select strip + (Master). In order to show a hidden strip, the hidden strips need to + be shown first using the /set_surface/strip_types 512 + command to show only hidden strips. Then use the + /strip/hide SSID 0 or + /select/hide 0 + to show that strip. Of course, because only hidden strips are showing, + the strip you have set to no long hide will seem to vanish. A + /set_surface/strip_types 159 will then show + the default strip types or replace the 159 with the desired strip_types. +

    +

    + When hiding more than one strip in a row, check the strip name before + hiding as the strips will move as each strip is hidden just as it does + with the GUI mixer. So to hide strips 5, 6 and 7, the hide button + for ssid 5 is pressed 3 times. A more intuitive method + would be to hide strips from right to left (7, 6 and 5) which will + work as expected. +

    + In short, shown strips can only be hidden when they are viewable and + hidden strip can only shown (or un-hid) when strip_types include hidden + strips.

    -

    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