From: Robin Gareus Date: Fri, 15 Apr 2016 20:38:00 +0000 (+0200) Subject: start documentation on strict-i/o and pin management X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;ds=sidebyside;h=b19b4b659ac86675696ff668d15ed70f2809d7c4;p=ardour-manual start documentation on strict-i/o and pin management --- diff --git a/_manual/14_signal-routing/08_role-of-jack.html b/_manual/14_signal-routing/08_role-of-jack.html deleted file mode 100644 index 4709cbb..0000000 --- a/_manual/14_signal-routing/08_role-of-jack.html +++ /dev/null @@ -1,13 +0,0 @@ ---- -layout: default -title: Role of JACK ---- - -

- Ardour uses JACK for all its internal signal flow except - between processors inside the same channel strip. This allows for a great - deal of flexibility in routing signals, but comes with an increased - latency penalty when using consecutive buses. -

- - diff --git a/_manual/14_signal-routing/08_signal-flow.html b/_manual/14_signal-routing/08_signal-flow.html new file mode 100644 index 0000000..ecd03e2 --- /dev/null +++ b/_manual/14_signal-routing/08_signal-flow.html @@ -0,0 +1,61 @@ +--- +layout: default +title: Track/Bus Signal Flow +--- +

Overview

+

+In each individual Track or Bus the signal flow is top to bottom. Consider the following diagram: +

+ +

track signal routing

+ +

+Trim, Fader and Panner are provided by Ardour. The Processor-Box can hold 3rd Party Plugins or host-provided redirects (insert, aux-send,..). +

+ +

+An important aspect is that the signal flow is multi-channel and not fixed throughout the track. For example, a Track can have a mono input, a mono to stereo plugin (e.g. reverb) flowing into a surround panner with 6 outputs. The design of Ardour is that width of the signal flow is defined by the passage through plugins in the processor box, followed by panning. +The number of inputs to the panner is defined by the number outputs of the last plugin in the chain. The number of panner outputs is equal to the track's outputs ports, which can be added and remove dynamically. This schema called Flexible I/O. It's very powerful and a distinct feature of Ardour. +

+ +

+The golden rule of processor signal flow:
The number of outputs of one link of the process chain defines the number inputs of the next, until the panner. +

+ +

+Due to this rule there is one very common case that is hard to achieve: Keep a mono track mono. With Flexible I/O, if a stereo plugin is added on a mono track, the signal flow after that plugin becomes stereo. +

+ +

Strict I/O

+

Strict I/O enforces a simple rule: Plugins have the same number of inputs as they have outputs. By induction the track will have as many output-ports as there are input ports.

+
    +
  1. Adding a Plugin will not modify the signal-flow. The number of plugin outputs is forced to the number of inputs present at the point of insertion. + If a plugin-pin is missing, it is ignored. If Plugin-pin is unconnected, it is fed with silence. Unconnected plugin outputs are ignored).
    2. +
  2. Strict I/O enforces the number of output ports. The number of inputs to the panner (outputs of last plugin) defines the number of track outputs (after panner). + Required ports are automatically added, excess ports are removed. The user cannot manually add/remove output ports.
    3. +
+ +

+Strict I/O is set when creating the track and can later be en/disabled dynamically in the context menu of every mixer strip. +

+ +

strict i/o routing

+ +

There are two exceptions to the above rule 1.

+ + +

Customizing the Signal Flow

+

+The signal flow though the mixer can be customized at every processor node via "Pin Configuration" in the context menu of every processor. +User customization override all automatic (flexible/strict i/o mode) inferred output port settings for the given processor. +Non-customized plugins downstream will follow suit depending on the selected route mode. e.g. adding an additional output to a plugin on a track set to strict-i/o will trickle down the process chain until the output and result in the addition of an output port. This is useful for example in case of a mono to stereo reverb. +

+ +

+One can also bypass plugin instances with a 'trhu' connection. This connection is latency compensated. One example is separate Left/Right channel Equalization using two mono plugins on a stereo track: +

+

separate left/right Eq

diff --git a/_manual/24_lua-scripting/01_brain_dump.html b/_manual/24_lua-scripting/01_brain_dump.html index fe3820b..6327e9a 100644 --- a/_manual/24_lua-scripting/01_brain_dump.html +++ b/_manual/24_lua-scripting/01_brain_dump.html @@ -4,7 +4,7 @@ title: Scripting Documentation ---

-This Documention is Work in Progress and far from complete. Also the documented API may be subject to change. +This Documentation is Work in Progress and far from complete. Also the documented API may be subject to change.

Preface

diff --git a/source/css/app.css b/source/css/app.css index 0809c64..114abf3 100644 --- a/source/css/app.css +++ b/source/css/app.css @@ -417,6 +417,10 @@ samp:after { clear:left; } +#content p.center { + text-align:center; +} + #content .note,.warning,.fixme { min-height: 20px; padding: 19px; diff --git a/source/images/left_right_eq.png b/source/images/left_right_eq.png new file mode 100644 index 0000000..a5ab53a Binary files /dev/null and b/source/images/left_right_eq.png differ diff --git a/source/images/pin_config_ctx_menu.png b/source/images/pin_config_ctx_menu.png new file mode 100644 index 0000000..ef520d2 Binary files /dev/null and b/source/images/pin_config_ctx_menu.png differ diff --git a/source/images/strict_io_routing.png b/source/images/strict_io_routing.png new file mode 100644 index 0000000..02d9c45 Binary files /dev/null and b/source/images/strict_io_routing.png differ diff --git a/source/images/track_signal_routing.png b/source/images/track_signal_routing.png new file mode 100644 index 0000000..f85403d Binary files /dev/null and b/source/images/track_signal_routing.png differ