X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;ds=sidebyside;f=include%2Fplaylist-operations.html;h=a05955783582f63ae395e7b62b76251728c6f129;hb=a26b49e5c69ac38d5465c62623994e8a81f1b6b3;hp=ee64f36e8e6845daf240491ddbce3a93d800ec07;hpb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;p=ardour-manual diff --git a/include/playlist-operations.html b/include/playlist-operations.html index ee64f36..a059557 100644 --- a/include/playlist-operations.html +++ b/include/playlist-operations.html @@ -1,67 +1,115 @@
- In the track header (editor window, left pane) is a button labelled p (for "Playlist"). If you click on this button, Ardour - displays the following menu: + In the track header (editor window, left pane) is a button labelled p (for "Playlist"). A click on this button displays the + following menu:
-- 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 Cowbell.1. 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 Lead Guitar, 2nd - take, vocals (quiet), - and downbeat cuica. Notice how these might be - different from the associated track names, which for these examples might - be Lead Guitar, - Vocals and Cuica. 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. +
(Local Playlists) | +Shows all of the playlists associated with this track, and indicates + the currently selected playlist | +
---|---|
Select… | +Allows switching playlists, either for this track or multiple ones (more about that later) | +
Rename… | +Displays a dialog to rename the current playlist |
New Playlist… | +Creates a new empty playlist, and the track switches to the new playlist | +
Copy Playlist… | +Creates a new playlist that is an independent copy of the current playlist; the track switches to the new playlist | +
Clear Current | +Removes all regions from the current playlist | +
Advanced | |
Copy from … | +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 | +
Share with … | +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 | +
Steal from … | +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 …" | +
+ When Stealing 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 (Local Playlists) list from the robbed track anymore, but + will now appear in the current track's local playlists.
+ +- If you are going to rename your playlists, do so before recording new - material to them. + It is entirely possible to share playlists 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 Playlist Use Cases.
-- It appears that recorded regions are not named after the playlist, but - after the track. +
+ 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 independent copy of it for that track, which can + then be edited without affecting the original.
-- It is entirely possible to share playlists 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 Select … + menu allows:
+- 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 independent copy of it for - that track. You can then edit this playlist without affecting the original. + When used for Only this track/group, in the + selector below, it is the same as using the New + Playlist … and Copy Playlist … from the + Playlist menu. +
++ But the selector also allows to apply these operation (changing + playlist, creating an empty new one or creating an independent copy) + for Rec-armed tracks or ALL tracks. This can be useful in a recording + situation with many microphones and multiple takes to deal with. +
++ These playlist operations, on multiple tracks, are also available + directly on the secondary toolbar in Recorder mode.
-