X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fplaylist-operations.html;fp=include%2Fplaylist-operations.html;h=c22f4dff18f94e121825c686aad916df565a3038;hb=2098e011e638b5c86c56e68df7757975fc4d728f;hp=0000000000000000000000000000000000000000;hpb=0e127ce41d7120d505f3aa9ae18dce679f403a3f;p=ardour-manual diff --git a/include/playlist-operations.html b/include/playlist-operations.html new file mode 100644 index 0000000..c22f4df --- /dev/null +++ b/include/playlist-operations.html @@ -0,0 +1,68 @@ + +
+ 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: +
++ 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. +
++ If you are going to rename your playlists, do so before recording new + material to them. +
++ It appears that recorded regions are not named after the playlist, but + after the track. +
+ ++ 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. +
++ 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. +
+ +