If this checkbox is enabled, tpf-client tries to communicate with Ardour through Ardour's OSC interface (which must be enabled in Ardour, of course). If tpf-client is able to talk Ardour, it is indicated by the "Ardour" box lighting up in green. When enabled, tpf-client sets strip labels in Ardour, manages JACK connections between tpf-client and Ardour and makes sure that Ardour displays only the stripts currently used in the session.
When enabled, tpf-client make sure that all necessary JACK audio connections from Ardour to tpf-client and from tpf-client to Ardour are created. This works dynamically as it takes into account the number of channels per peer and the number of peer slots, but also the strip mapping in the template session of Ardour. Ardour's and tpf-client's layout don't necessarily need to match for this work. This option has an impact only when the Ardour interface is enabled.
When enabled, tpf-client sends OSC commands to Ardour to hide unused strips so that only active strips remain visible. Active strips are those belonging to an occupied peer slot in tpf-client. Also, the number of strips shown for each peer reflects how many channels are received from that peer. When the option is disabled, all hidden strips are shown so that all strips are visible. This option has an impact only when the Ardour inteface is enabled.
tpf-client allows to assign labels to the local (or: source) channels. This
is done in the top section of the Ardour panel (see Set Ardour Local Strip Name).
The labels appear in Ardour on the strips connected tpf-client's inputs.
They are also synchronized with remote peers so that their Ardour uses the
labels for the strips carrying our signal. Of course, this means we also
see the the strips with the signal from the remote peers showing the labels
the remote peers gave to their channels.
This section is relevant only if you intend to create Ardour templates that are meant for tpf-client to interact with through the Ardour interface featue. This section explains how tpf-client identifies the different kinds of strips.
All strips from the group to_TPF are connected to the inputs of
tpf-client until either the strips of the group named to_TPF or
the input channels of tpf-client are depleted.
All outputs from the peer of the first slot are connected to the inputs of the strip named LOC-A, the outputs of the seconds slot to inputs of the strip named LOC-B, etc. This happens for each peer slot until either the input channels of the strip in Ardour or the number of outputs in tpf-client is depleted. Also, this happens for as many peer slots as are available or as many input strips following the LOC-X name scheme as are available.
The first two groups of strips is identified by their group name, namely
Inputs. Individual channels are identified by their strip ID. tpf-client
applies the labels that can be configured in the Ardour panel to the
strips of this group
The mechanism for identifying those strips is based on group membership.
Strips that are members of the group to_TPF are considered
input channels for tpf-client.
The peer strips (the ones that collect all channels from a peer output of tpf-client) are identified by their strip name. tpf-client assumes the following naming convention:
- LOC-A
- LOC-B
- LOC-C
- etc. tpf-client uses the strip's group label to display the peer's name.
The group Mixer collects all channels from tpf-client's outputs. They
carry the individual signals received from remote peers (as opposed to the
strips of the previous section which carry all signals of a remote peer in
one multi-channel strip). tpf-client applies the labels which remote peers
set to their own channels to those strips. tpf-clients determines the signal
source by following the JACK connections. Each channel is identified by the
multichannel strip its input is connected to (remote peer) and its position
therein (nth channel of remote peer x).