X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fosc58-personal-monitoring-control.html;h=65239dee93c9636346aa72b21021ff6da296bb87;hb=fa57e2e828168790a9cc737400d2a9d162fd93cb;hp=2c948c370bfdeee31727f502343ba1971e06f84c;hpb=2098e011e638b5c86c56e68df7757975fc4d728f;p=ardour-manual diff --git a/include/osc58-personal-monitoring-control.html b/include/osc58-personal-monitoring-control.html index 2c948c3..65239de 100644 --- a/include/osc58-personal-monitoring-control.html +++ b/include/osc58-personal-monitoring-control.html @@ -1,7 +1,7 @@

Personal monitoring can allow a performer with a smart phone to set - their personal monitor mix for a floor wedge or inear monitoring. + their personal monitor mix for a floor wedge or in-ear monitoring. In Ardour 5.6 OSC commands to allow this were added.

Setup

@@ -18,7 +18,7 @@
  • Connect the output of that bus to one of the audio interface's playback ports that is not otherwise used. OSC - will now include this bus in it's list of aux buses as it + will now include this bus in it's list of aux busses as it no longer has it's output connected to the Master bus.
  • @@ -46,6 +46,37 @@ /cue. It is expected that a surface used as a personal monitor control will use only /cue commands.

    +

    + Most phone OSC applets (TouchOSC, Control) require manual port to be set. + There are certainly more controls than needed. Using send enables for + example, may lead to wasted time discovering why a send has no sound. + A good easy to use controller that fits on most phones while still + being controllable even with big fingers might look like: +

    + + + + + +
    +
    + TouchOSC Screenshot +
    Personal Monitor controller using TouchOSC
    +
    +     		+
    + Control Screenshot +
    Personal Monitor controller using Control
    +
    +
    + +

    + Ardour is not limited to talking to one personal monitor controller + at a time, but is able to deal with many simultaneously, each controlling + it's own Aux bus. +

    The send controls and feedback all have the send id (1 to n) in line as part of the OSC path. So the path for the second send would be @@ -53,56 +84,55 @@ most surfaces used for this will only be able to handle one parameter.

    Commands

    -
    -
    /cue/connect
    -
    Returns a list of aux buses.
    -
    /cue/aux aux-number
    -
    where aux-number is an integer which is the aux bus - number this surface will use.
    -
    /cue/next_aux
    -
    Sets the the aux bus to one bus higher.
    -
    /cue/previous_aux
    -
    Sets the aux to one bus lower.
    -
    /cue/connect
    -
    Returns a list of aux buses.
    -
    /cue/fader position
    -
    where position is a float for the position of the fader - between 0.0 and 1.0.
    -
    /cue/mute state
    -
    where state is a float of 0.0 for mute off and 1.0 for mute on.
    -
    /cue/send/fader/id position
    -
    where position is a float for the position of the fader - between 0.0 and 1.0.
    -
    /cue/send/enable/id state
    -
    where state is a float of 0.0 for disable and 1.0 for enable.
    -
    + + + + + + + + + + + + + + + + + +
    /cue/connectReturns a list of aux busses and connects to the first.
    /cue/aux aux-numberwhere aux-number is an integer or float which is the aux bus + number this surface will use.
    /cue/next_auxSets the the aux bus to one bus higher.
    /cue/previous_auxSets the aux to one bus lower. This can also be used as a "connect" + button to save space in a phone layout.
    /cue/fader positionwhere position is a float for the position of the fader + between 0.0 and 1.0.
    /cue/mute statewhere state is a float of 0.0 for mute off and 1.0 for the Aux bus mute on.
    /cue/send/fader/id positionwhere position is a float for the position of the fader + between 0.0 and 1.0.
    /cue/send/enable/id statewhere state is a float of 0.0 for disable and 1.0 for enable.

    Feedback

    -
    -
    /cue/name name
    -
    where name is a string that is the name of the currently - selected aux bus.
    -
    /cue/name/id name
    -
    where name is a string that is the name of the aux bus - that id belongs to.
    -
    /cue/fader position
    -
    where position is a float from 0.0 to 1.0 that shows the - fader position for the selected aux bus.
    -
    /cue/mute state
    -
    where state is a float of 0.0 or 1.0 that shows the state - of the mute for the selected aux bus.
    -
    /cue/signal activity
    -
    where activity is a float of 0.0 or 1.0 that shows audio - activity for the selected aux bus.
    -
    /cue/send/name/id name
    -
    where name is a string that is the name of the channel - that send id belongs to.
    -
    /cue/send/fader/id position
    -
    where position is a float from 0.0 to 1.0 that is the position - for the fader for the send that id belongs to.
    -
    /cue/send/enable/id state
    -
    where state is a float of 0.0 or 1.0 that is the state - of the enable for the send that id belongs to.
    -
    + + + + + + + + + + + + + + + + + +
    /cue/name namewhere name is a string that is the name of the currently + selected aux bus.
    /cue/name/id namewhere name is a string that is the name of the aux bus + that id belongs to.
    /cue/fader positionwhere position is a float from 0.0 to 1.0 that shows the + fader position for the selected aux bus.
    /cue/mute statewhere state is a float of 0.0 or 1.0 that shows the state + of the mute for the selected aux bus.
    /cue/signal activitywhere activity is a float of 0.0 or 1.0 that shows audio + activity for the selected aux bus.
    /cue/send/name/id namewhere name is a string that is the name of the channel + that send id belongs to.
    /cue/send/fader/id positionwhere position is a float from 0.0 to 1.0 that is the position + for the fader for the send that id belongs to.
    /cue/send/enable/id statewhere state is a float of 0.0 or 1.0 that is the state + of the enable for the send that id belongs to.

    While a fader is being adjusted, the corresponding /*/name text will give the level in db.