X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Ftrack-types.html;h=4a09d241f0b96bfef4c481abc85d5379d93dfe22;hb=d1339ef8a461372e6abf8bbfd918cbbc0c65c903;hp=e463f6aaac514c64462a08b653fd076a048edef7;hpb=3ac2b1ab0af5ff2d380c60cad295cbced589602f;p=ardour-manual diff --git a/include/track-types.html b/include/track-types.html index e463f6a..4a09d24 100644 --- a/include/track-types.html +++ b/include/track-types.html @@ -1,6 +1,6 @@
- Ardour offers three track types depending on the type of + Ardour offers three track types depending on the type of data they contain, and differentiates between three track modes, depending on their recording behaviour.
@@ -8,53 +8,53 @@An Ardour track can be of type audio or MIDI, - depending on the data that the track will primarily record - and play back. However, either type of track can pass either + depending on the data that the track will primarily record + and play back. However, either type of track can pass either type of data. Hence, for example, one might have a MIDI track that - contains an instrument plugin; such a track would record and play back - MIDI data from disk but would produce audio, since the instrument plugin + contains an instrument plugin; such a track would record and play back + MIDI data from disk but would produce audio, since the instrument plugin would turn MIDI data into audio data.
- Nevertheless, when adding tracks to a session, you typically have an idea - of what you need to use the new tracks for, and Ardour offers you three + Nevertheless, when adding tracks to a session, you typically have an idea + of what you need to use the new tracks for, and Ardour offers you three choices:
If you add an instrument plugin, the MIDI track outputs audio instead of MIDI data.
- Audio tracks in Ardour have a mode which affects how they behave + Audio tracks in Ardour have a mode which affects how they behave when recording:
- The screenshot on the right shows the subtle difference between an overdub
- in normal mode (upper track) and one in non-layered mode
+ The screenshot on the right shows the subtle difference between an overdub
+ in normal mode (upper track) and one in non-layered mode
(lower track). Both tracks were created using identical audio data.
The upper track shows a new region which has been layered on
- top of the the existing (longer) region. You can see this if you look
+ top of the the existing (longer) region. You can see this if you look
carefully at the region name strips.
The lower track has split the existing region in two, trimmed each new
- region to create space for the new overdub, and inserted the overdub region
- in between.
+ region to create space for the new overdub, and inserted the overdub region
+ in between.
- Ardour tracks can have any number of inputs and any number of outputs, and the
- number of either can be changed at any time (subject to restrictions caused by
- any plugins in a track). However it is useful to not have to configure this sort
- of thing for the most common cases, and so the
- Add Tracks dialog allows you to
+ Ardour tracks can have any number of inputs and any number of outputs, and the
+ number of either can be changed at any time (subject to restrictions caused by
+ any plugins in a track). However it is useful to not have to configure this sort
+ of thing for the most common cases, and so the
+ Add Tracks dialog allows you to
select "Mono", "Stereo" and few other typical multichannel presets
The name of the preset describes the number of input channels
of the track or bus.
@@ -107,17 +107,17 @@
inputs of the master bus,
to which the track outputs will be connected.
- For example, if you have a two-channel master bus, then a Mono track has one
+ For example, if you have a two-channel master bus, then a Mono track has one
input and two outputs; a Stereo track has two inputs and two outputs.
If you you set Edit > Preferences > Audio > Connection of Tracks and Busses to manual, then tracks will be left disconnected by default - and there will be as many outputs as there are inputs. It is up to you to connect - them as you wish. This is not a particularly useful way to work unless you are doing - something fairly unusual with signal routing and processing. It is almost always - preferable to leave Ardour to make connections automatically, even if you later + and there will be as many outputs as there are inputs. It is up to you to connect + them as you wish. This is not a particularly useful way to work unless you are doing + something fairly unusual with signal routing and processing. It is almost always + preferable to leave Ardour to make connections automatically, even if you later change some of them manually.