X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Faudiomidi-busses-mixer-strips.html;h=48e0f3c5d793dd52c5ee9dc637be12dbebe82f18;hb=d3016470f888ab4b0ee20d7e5040f4b37a655c3c;hp=e1261aec9ee4cb2454463686911db3d322968f65;hpb=966c1e41453663b930889961712641c1864d8ae3;p=ardour-manual diff --git a/include/audiomidi-busses-mixer-strips.html b/include/audiomidi-busses-mixer-strips.html index e1261ae..48e0f3c 100644 --- a/include/audiomidi-busses-mixer-strips.html +++ b/include/audiomidi-busses-mixer-strips.html @@ -7,9 +7,9 @@ An Ardour bus can be considered a virtual track, as in a track that doesn't have a playlist (so, no regions). Its use is to "group" some audio signals to be treated the same way. One simple use case is to group all the audio tracks - containing the different drums of a drumkit. Routing all the drums tracks + containing the different drums of a drum kit. Routing all the drum tracks' outputs to a bus allows, once the different levels amongst the drums have been - set, to adjust the global level of the drumkit in the mix. + set, to adjust the global level of the drum kit in the mix.

Bus usage goes way beyond this simple example though: busses, as tracks, can @@ -33,7 +33,7 @@

  • as for tracks, the MIDI bus doesn't have a trim knob or invert phase button(s).

    • - MIDI busses provide a particularly efficient workflow for virtual drumkits where + MIDI busses provide a particularly efficient workflow for virtual drum kits where the arrangement uses different MIDI tracks. Moreover, busses with both Audio and MIDI inputs are well suited for vocoders and similar plugins, where a MIDI signal controls an audio one. @@ -48,7 +48,7 @@ all of their controls. The differences are: