3 title: Playlist Operations
7 In the track header (editor window, left pane) is a button labelled <kbd
8 class="menu">p</kbd> (for "Playlist"). If you click on this button, Ardour
9 displays the following menu:
11 <dl class="wide-table">
12 <dt>(Local Playlists)</dt>
13 <dd>Shows all of the playlists associated with this track, and indicates
14 the currently selected playlist</dd>
16 <dd>Displays a dialog to rename the current playlist</dd>
18 <dd>Creates a new empty playlist, and the track switches to the new playlist</dd>
20 <dd>Creates a new playlist that is a copy of the current playlist; the track switches to the new playlist</dd>
21 <dt>Clear Current</dt>
22 <dd>Removes all regions from the current playlist</dd>
23 <dt>Select From All</dt>
24 <dd>Displays a playlist browser to manually choose which playlist this track should use. (You can even select playlists from other tracks here)</dd>
27 <h2>Renaming Playlists</h2>
29 Playlists are created with the name of the track of which they are
30 associated, plus a version number. So, the first playlist for a track
31 called "Cowbell" will be called <samp>Cowbell.1</samp>. This name will
32 be used to define the names of any regions added to the playlist by
33 recording. You can change the name at any time, to anything you want.
34 Ardour does not require that your playlist names are all unique, but it
35 will make your life easier if they are. Suggested examples of user-assigned
36 names for a playlist might include <kbd class="input">Lead Guitar, 2nd
37 take</kbd>, <kbd class="input">vocals (quiet)</kbd>,
38 and <kbd class="input">downbeat cuica</kbd>. Notice how these might be
39 different from the associated track names, which for these examples might
40 be <kbd class="input">Lead Guitar</kbd>,
41 <kbd class="input">Vocals</kbd> and <kbd class="input">Cuica</kbd>. The
42 playlist name provides more information because it is about a specific
43 version of the material that may (or may not) end up in the final version
47 If you are going to rename your playlists, do so before recording new
51 It appears that recorded regions are not named after the playlist, but
55 <h2>Sharing Playlists</h2>
57 It is entirely possible to <dfn>share playlists</dfn> between tracks. The only
58 slightly unusual thing you may notice when sharing is that edits to the
59 playlist made in one track will magically appear in the other. If you
60 think about this for a moment, its an obvious consequence of sharing.
61 One application of this attribute is parallel processing, described
65 You might not want this kind of behaviour, even though you still want
66 two tracks to use the same (or substantially the same) playlist. To
67 accomplish this, select the chosen playlist in the second track, and
68 then use New Copy to generate an <dfn>independent copy</dfn> of it for
69 that track. You can then edit this playlist without affecting the original.
72 <h3>Using Playlists for Parallel Processing</h3>
74 One of the uses of playlists is to apply multiple effects to the same
75 audio stream. For example, let's say you would like to apply two
76 different non-linear effects such as distortion or compression to the
77 same audio source (for linear effects, you could just apply them one after
78 the other in the same track).<br />
79 Create a new track, apply the original track's playlist, and
80 then apply effects to both tracks independently.
83 The same result could be achieved by feeding your track to multiple busses which
84 then contain the processing, but this increases the overall latency,
85 complicates routing and uses more space in the Mixer window.
88 <h2>Using Playlists for "Takes"</h2>
90 Using Playlists for <dfn>takes</dfn> is a good solution if you are going
91 to need the ability to edit individual takes, and select between them,
92 but you won't be compositing multiple takes together.
95 Each time you start a new take, create a new playlist with
96 <kbd class="menu">p > New</kbd>
97 Later, you can Select your way back to previous or later takes as
101 If you want to record multiple takes and then "comp" between them, it
102 is probably better to simply record each successive take on top of the
103 others in "layers" and then edit them using the layer tools, explained
107 <h2>Using Playlists for Multi-Language Productions</h2>
109 The same approach as for takes is useful when you are recording or
110 editing content in multiple versions, such as dubbed movie dialog in
111 several languages, and you want all versions on the same track, to
112 get the same processing. <br />
113 Select the appropriate language before exporting the session.