<p>
- In the track header (editor window, left pane) is a button labelled <kbd
- class="menu">p</kbd> (for "Playlist"). If you click on this button, Ardour
- displays the following menu:
+ In the <a href="@@audio-track-controls">track header</a> (editor window, left pane) is a button labelled <kbd
+ class="menu">p</kbd> (for "Playlist"). A click on this button displays the
+ following menu:
</p>
-<dl class="wide-table">
- <dt>(Local Playlists)</dt>
- <dd>Shows all of the playlists associated with this track, and indicates
- the currently selected playlist</dd>
- <dt>Rename</dt>
- <dd>Displays a dialog to rename the current playlist</dd>
- <dt>New</dt>
- <dd>Creates a new empty playlist, and the track switches to the new playlist</dd>
- <dt>New Copy</dt>
- <dd>Creates a new playlist that is a copy of the current playlist; the track switches to the new playlist</dd>
- <dt>Clear Current</dt>
- <dd>Removes all regions from the current playlist</dd>
- <dt>Select From All</dt>
- <dd>Displays a playlist browser to manually choose which playlist this track should use. (You can even select playlists from other tracks here)</dd>
-</dl>
-<h2>Renaming Playlists</h2>
-<p>
- Playlists are created with the name of the track of which they are
- associated, plus a version number. So, the first playlist for a track
- called "Cowbell" will be called <samp>Cowbell.1</samp>. This name will
- be used to define the names of any regions added to the playlist by
- recording. You can change the name at any time, to anything you want.
- Ardour does not require that your playlist names are all unique, but it
- will make your life easier if they are. Suggested examples of user-assigned
- names for a playlist might include <kbd class="input">Lead Guitar, 2nd
- take</kbd>, <kbd class="input">vocals (quiet)</kbd>,
- and <kbd class="input">downbeat cuica</kbd>. Notice how these might be
- different from the associated track names, which for these examples might
- be <kbd class="input">Lead Guitar</kbd>,
- <kbd class="input">Vocals</kbd> and <kbd class="input">Cuica</kbd>. The
- playlist name provides more information because it is about a specific
- version of the material that may (or may not) end up in the final version
- of the track.
+<table class="dl">
+ <tr>
+ <th><i>(Local Playlists)</i></th>
+ <td>Shows all of the playlists associated with this track, and indicates
+ the currently selected playlist</td>
+ </tr>
+ <tr>
+ <th>Select…</th>
+ <td>Allows switching playlists, either for this track or multiple ones (more about that later)</td>
+ </tr>
+ <tr>
+ <th>Rename…</th>
+ <td>Displays a dialog to rename the current playlist</td></tr>
+ <tr>
+ <th>New Playlist…</th>
+ <td>Creates a new empty playlist, and the track switches to the new playlist</td>
+ </tr>
+ <tr>
+ <th>Copy Playlist…</th>
+ <td>Creates a new playlist that is an independent copy of the current playlist; the track switches to the new playlist</td>
+ </tr>
+ <tr>
+ <th>Clear Current</th>
+ <td>Removes all regions from the current playlist</td>
+ </tr>
+ <tr>
+ <th>Advanced</th><td></td></tr>
+ <tr>
+ <th class="sub1">Copy from …</th>
+ <td>Creates a new playlist that is an independent copy of a playlist from this track or another one; the track switches to the new playlist</td>
+ </tr>
+ <tr>
+ <th class="sub1">Share with …</th>
+ <td>Uses a playlist from this track or another one; any edit to this playlist will be reflected on the other track(s) that use this playlist</td>
+ </tr>
+ <tr>
+ <th class="sub1">Steal from …</th>
+ <td>Uses a playlist from this track or another one and removes it from the local playlists in the "robbed" track. Otherwise, behaves like "Share with …"</td>
+ </tr>
+</table>
+
+<p class="note">
+ When <em>Stealing</em> a playlist, it does not remove the playlist from the
+ robbed track. The playlist now belongs to the current track, and the robbed track
+ uses the playlist as a shared playlist with the new owner. Hence, this playlist
+ won't be in the <i>(Local Playlists)</i> list from the robbed track anymore, but
+ will now appear in the current track's local playlists.
</p>
+
+<h2>Sharing vs copying Playlists</h2>
<p>
- If you are going to rename your playlists, do so before recording new
- material to them.
+ It is entirely possible to <dfn>share playlists</dfn> between tracks. The only
+ slightly unusual thing that should be noted when sharing is that edits to the
+ playlist made in one track will magically appear in the other. It is an
+ obvious consequence of sharing. One application of this attribute is parallel
+ processing, described in <a href="@@playlist-usecases">Playlist Use Cases</a>.
</p>
-<p class="fixme">
- It appears that recorded regions are not named after the playlist, but
- after the track.
+<p>
+ To avoid this kind of behaviour, and nevertheless use the same (or substantially
+ the same) playlist on two tracks, the desired playlist must be copied and not shared.
+ This generates an <dfn>independent copy</dfn> of it for that track, which can
+ then be edited without affecting the original.
</p>
-<h2>Sharing Playlists</h2>
+<h2>Select menu</h2>
+
+<figure>
+ <img src="/images/playlist_select.png" alt="The Select playlist menu"/>
+ <figcaption>The Select playlist menu.</figcaption>
+</figure>
+
<p>
- It is entirely possible to <dfn>share playlists</dfn> between tracks. The only
- slightly unusual thing you may notice when sharing is that edits to the
- playlist made in one track will magically appear in the other. If you
- think about this for a moment, its an obvious consequence of sharing.
- One application of this attribute is parallel processing, described
- below.
+ In its most basic use, the <kbd class="menu">Select …</kbd>
+ menu allows:
</p>
+<ul>
+ <li>
+ to switch from one playlist to another (with the added benefit,
+ compared to switching directly from the <i>Local Playlists</i>
+ list, to see the creation date and time),
+ </li>
+ <li>
+ to create a new, empty playlist, with the <kbd class="menu">New
+ Playlist(s)</kbd> button,
+ </li>
+ <li>
+ or to create an independent copy of the current one, with the
+ <kbd class="menu">Copy Playlist(s)</kbd> button.
+ </li>
+</ul>
<p>
- You might not want this kind of behaviour, even though you still want
- two tracks to use the same (or substantially the same) playlist. To
- accomplish this, select the chosen playlist in the second track, and
- then use New Copy to generate an <dfn>independent copy</dfn> of it for
- that track. You can then edit this playlist without affecting the original.
+ When used for <kbd class="option">Only this track/group</kbd>, in the
+ selector below, it is the same as using the <kbd class="menu">New
+ Playlist …</kbd> and <kbd class="menu">Copy Playlist …</kbd> from the
+ Playlist menu.
+</p>
+<p>
+ But the selector also allows to apply these operation (changing
+ playlist, creating an empty new one or creating an independent copy)
+ for <kbd class="option">Rec-armed tracks</kbd> or <kbd
+ class="option">ALL tracks</kbd>. This can be useful in a recording
+ situation with many microphones and multiple takes to deal with.
+</p>
+<p>
+ These playlist operations, on multiple tracks, are also available
+ directly on the secondary toolbar in <a
+ href="@@recorder">Recorder</a> mode.
</p>
-
-
projects / ardour-manual / blobdiff