3 Ardour can be used in many different ways, from extremely simple to extremely
4 complex. Many projects can be handled using the following kind of
8 <h2>Stage 1: Creating The Project</h2>
11 The first step is to create a new <dfn>session</dfn>, or open an existing
12 one. A session consists of a folder containing a session file that defines
13 all the information about the session. All media files used by the session
14 are usually stored within the session folder.
18 More details on sessions can be found in <a href="@@sessions">Sessions</a>
22 <h2>Stage 2: Creating and Importing Audio and MIDI Data</h2>
25 Once a session has been created, it will be necessary to add some audio
26 and/or MIDI material to it—which can be done in one of 3 ways:
30 <li><dfn>Record</dfn> incoming audio or MIDI data, either via audio or MIDI
31 hardware connected to the computer, or from other applications</li>
32 <li><dfn>Create</dfn> new MIDI data using the mouse and/or various dialogs
34 <li><dfn>Import</dfn> existing media files into the session</li>
38 <dfn>MIDI recordings</dfn> consist of performance data ("play note X at time
39 T") rather than actual sound. As a result, they are more flexible than actual
40 audio, since the precise sound that they will generate when played depends on
41 where the MIDI data is sent to. Two different synthesizers may produce very
42 different sounds in response to the same incoming MIDI data.
46 <dfn>Audio recordings</dfn> can be made from external instruments with
47 electrical outputs (keyboards, guitars, etc.), or via microphones or other sound capturing equipment.
51 Ardour uses the <dfn>JACK Audio Connection Kit</dfn> for all audio and MIDI
52 I/O, which means that recording audio/MIDI from other applications is
53 fundamentally identical to recording audio/MIDI from audio/MIDI hardware.
56 <p class=fixme>Sanity check: is this true anymore? Does Ardour's ALSA backend make this statement not exactly true?</p>
58 <h2>Stage 3: Editing and Arranging</h2>
61 Once there is material within the session, it can be arranged in time. This
62 is done in one of the two main windows of Ardour: the <dfn>Editor</dfn>
67 Audio/MIDI data appears in chunks called <dfn>regions</dfn>, which are
68 arranged into horizontal lanes called <dfn>tracks</dfn>. Tracks are stacked
69 vertically in the Editor window. Regions can be copied, shortened, moved, and
70 deleted without changing the actual data stored in the session at
71 all—Ardour is a <dfn>non-destructive</dfn> editor. (Almost) nothing
72 done while editing will ever modify the files stored on disk (with the
73 exception of the session file itself).
77 Many <dfn>transformations</dfn> can be done to the contents of regions, again
78 without altering anything on disk. It is possible to alter, move, and delete
79 MIDI notes, and remove silence from audio regions, for example.
82 <p class=fixme>Sanity check: deleting MIDI notes doesn't change them on disk? Isn't anything done to MIDI a destructive operation?</p>
84 <h2>Stage 4: Mixing and Adding Effects</h2>
87 Once the arrangement of the session mostly complete, the next step is the
88 <dfn>mixing</dfn> phase. Mixing is a broad term to cover the way the audio
89 signals that the session generates during playback are processed and added
90 together into a final result that is actually heard. It can involve altering
91 the relative levels of various parts of the session, adding effects that
92 improve or transform certain elements, and others that bring the sound of the
93 whole session to a new level.
97 Ardour allows <dfn>automation</dfn> of changes to any mixing parameters (such
98 as volume, panning, and effects controls)—it will record the changes
99 made over time, using a mouse or keyboard or some external control device,
100 and can play back those changes later. This is very useful because often the
101 settings needed will vary in one part of a session compared to
102 another—rather than using a single setting for the volume of a track,
103 it may need increases followed by decreases (for example, to track the
104 changing volume of a singer). Using automation can make all of this
108 <h2>Stage 5: Export</h2>
111 Once the arrangement and mix of the session is finalized, a single audio file
112 that contains a ready-to-listen to version of the work is usually desired.
113 Ardour allows the <dfn>exporting</dfn> of audio files in a variety of formats
114 (simultaneously in some cases). This exported file would typically be used in
115 creating a CD, or be the basis for digital distribution of the work.
119 Of course it is sometimes desirable to export material that isn't finished
120 yet—for example, to give a copy to another party to mix on their own
121 system. Ardour allows exporting as much of a session as desired, at any
122 time, in any supported format.