copy edits to Playlist pages, link correction for track types page

_manual/09_working-with-playlists/01_understanding-playlists.html

@@ -7,10 +7,12 @@ title: Understanding Playlists
   
   
 <p>A playlist is a list of regions ordered in time. It defines which parts of which source files should be played and when.  Playlists are a fairly advanced topic, and can be safely ignored for many types of audio production, however the use of playlists allows the audio engineer more flexibility for tasks like multiple takes of a single instrument, alternate edits of a given recording, parallel effects such as reverb or compression, and other tasks.</p>
-<p>Each audio track in Ardour is really just a mechanism for taking a playlist and generating the audio stream that it represents. As a result, editing a track really means modifying its playlist in some way. Since a playlist is a list of regions, most of the modifications involve manipulating regions: their position, length and so forth. This is covered in the chapter about regions. Here, we cover some of the things you can do with playlists as objects in their own right.</p>
+<p>Each audio track in Ardour is really just a mechanism for taking a playlist and generating the audio stream that it represents. As a result, editing a track really means modifying its playlist in some way. Since a playlist is a list of regions, most of the modifications involve manipulating regions: their position, length and so forth. This is covered in the chapter <a href="/working-with-regions/">Working With Regions</a>. Here, we cover some of the things you can do with playlists as objects in their own right.</p>
+
 <h3>Tracks are not Playlists</h3>
 <p>It is important to understand that a track is not a playlist. A track has a  playlist.  A track is a mechanism for generating the audio stream represented by the playlist and passing it through a signal processing pathway. At any point in time, a track has a single playlist associated with it. When the track is used to record, that playlist will have one or more new regions added to it. When the track is used for playback, the contents of the playlist will be heard. You can change the playlist associated with a track at (almost) any time, and even share playlists between tracks.</p>
-<p>If you have some experience of other DAWs, then you might have come across the term "virtual track", normally defined as a track that isn't actually playing or doing anything, but can be mapped/assigned to a "real track". This concept is functionally identical to Ardour's playlists. We just like to be little more clear about what is actually happening rather than mixing old and new terminology ("virtual" and "track") into confusing terminology.</p>
+<p>If you have some experience of other <acronym title="Digital Audio Workstations">DAWs</acronym>, then you might have come across the term "virtual track", normally defined as a track that isn't actually playing or doing anything, but can be mapped/assigned to a "real track". This concept is functionally identical to Ardour's playlists. We just like to be little more clear about what is actually happening rather than mixing old and new terminology ("virtual" and "track") into confusing terminology.</p>
+
 <h3>Playlists are Cheap</h3>
-<p>One thing you should be clear about is that playlists are cheap. They don't cost anything in terms of CPU consumption, and they have very minimal efforts on memory use. Don't be afraid of generating new playlists whenever you want to. They are not equivalent to tracks, which require extra CPU time and significant memory space, or audio files, which use disk space, or to plugins that require extra CPU time. If a playlist is not in use, it occupies a small amount of memory, and nothing more.</p>
+<p>One thing you should be clear about is that playlists are cheap. They don't cost anything in terms of CPU consumption, and they have very minimal efforts on memory use. Don't be afraid of generating new playlists whenever you want to. They are not equivalent to tracks, which require extra CPU time and significant memory space, or audio files, which use disk space, or plugins that require extra CPU time. If a playlist is not in use, it occupies a small amount of memory, and nothing more.</p>
   

_manual/09_working-with-playlists/02_playlist-operations.html

@@ -21,14 +21,18 @@ title: Playlist Operations
 <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>
+
 <h3>Renaming Playlists</h3>
 <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 "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.</p>
 <p>If you are going to rename your playlists, do so before recording new material to them.</p>
+
 <h3>Sharing Playlists</h3>
-<p>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 parrallel processing, described below.</p>
+<p>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.</p>
 <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 independent copy of it for that track. You can then edit this playlist without affecting the original.</p>
+
 <h3>Using Playlists for "Parallel Processing"</h3>
-<p>One of the uses of Playlists is to apply multiple effects to the same audio stream.  For example, let's say you have a track and you'd like to apply a second set of effects, at the same time to the original track.  In this case you could make a new track, select the original track's Playlist, and then apply different effects to the second track than the first (including panning, inserts, and bussing changes).  Now, if you edit either of the track's playlists, the changes will appear in both tracks.</p>
+<p>One of the uses of Playlists is to apply multiple effects to the same audio stream. For example, let's say you would like to apply two different effects to the same audio source. have a track and you'd like to apply a second set of effects, at the same time to the original track.  In this case you could make a new track, select the original track's Playlist, and then apply different effects to the second track than the first (including panning, inserts, and bussing changes).  Now, if you edit either of the track's playlists, the changes will appear in both tracks.</p>
+
 <h3>Using Playlists for "Takes"</h3>
 <p>Using Playlists for takes is a good solution if you are going to need the ability to edit individual takes, and select between them, but you won't be "compositing" multiple takes together.  This might be the case if you were recording multiple languages of a given track, and you want to use the same "track" for each language so that they get the same processing.  Then you select each language before exporting the mix for each separate language.</p>
 <p>You use the Clear Current operation each time you want to start a new take. This is a non-destructive operation that removes all existing regions from the current playlist. Although you won't lose any information doing this, its probably not appropriate unless the last take was so awful that you want to discard it (although without the finality of Remove Last Capture ). Finally, and probably most useful, you can use the New operation in the playlist button menu to create a new empty playlist, ready for the next take. Later, you can Select your way back to previous or later takes as desired, either in this or some other track.</p>

_manual/10_working-with-tracks/01_track-types.html

@@ -6,7 +6,7 @@ title: Track Types
 
   
   <h2>Data Type</h2>
-<p>An Ardour track can be either ‘audio’ or ‘MIDI’. The only real difference between the two is the type of data that the track will record and play back. Either type of track can pass either type of data. Hence, for example, one might have a MIDI track that contains an instrument plugin; such a track would record and playback MIDI data from disk but would produce audio, since the instrument would turn the one into the other. </p>
+<p>An Ardour track can be either ‘audio’ or ‘MIDI’. The only real difference between the two is the type of data that the track will record and play back. Either type of track can pass either type of data. Hence, for example, one might have a MIDI track that contains an instrument plugin; such a track would record and play back MIDI data from disk but would produce audio, since the instrument plugin would turn MIDI data into audio data.</p>
 <p>Nevertheless, when adding tracks to a session, you typically have an idea of what you need to use the new tracks for, and Ardour offers you three choices:</p>
 <dl class="narrower-table">
 <dt>Audio Tracks</dt>
@@ -16,6 +16,7 @@ title: Track Types
 <dt>Audio/MIDI Tracks</dt>
 <dd>There are a few notable plugins that can usefully accept both audio and MIDI data (Reaktor is one, and various "auto-tune" like plugins are another example.  It can be tricky to configure this type of track manually, so Ardour allows you to select this track type specifically for use when working with such plugins. It is <strong>not</strong> generally the right choice when working normal MIDI tracks, and a dialog will warn you of this.</dd>
 </dl>
+
 <h2>Track Modes</h2>
 <p>Audio tracks in Ardour can have a "mode" which affects how they behave when recording. </p>
 <dl class="narrower-table">
@@ -30,8 +31,8 @@ title: Track Types
 </dl>
 <p>Below is a screenshot that shows the subtly different results of an overdub in normal and non-layered mode. Both tracks were created using identical audio data. The upper track is in normal mode, and the overdub (the middle shorter region) has created a new region which if you look carefully has been layered on top of the the existing (longer) region. The lower track is in non-layered mode, and rather than overlay the overdub region, it split the existing region and inserted the new one in between. </p>
 <p><img src="/files/a3/a3_nonlayered_example.png" alt="normal and non-layered overdubbing comparision"></p>
-<p><a name="#channelconfiguration"><br><h2>Channel Configuration</h2>
-<p></p></a></p>
+
+<h2 id="channelconfiguration">Channel Configuration</h2>
 <p>Ardour tracks can have any number of inputs and any number of outputs, and the number of either can be changed at any time (subject to restrictions caused by any plugins in a track). However it is useful to not have to configure this sort of thing for the most common cases, and so the <a href="/working-with-tracks/adding-tracks">Add Tracks</a> dialog allows you to select "Mono", "Stereo" and few other typical configurations.</p>
 <h3>What does Mono or Stereo actually mean?</h3>
 <p>Given that tracks have a certain number of inputs and a certain number of outputs and that these numbers may not necessarily be the same, it is not immediately clear what terms like "Mono" or "Stereo" mean. Most people will know that they refer to "1 channel" and "2 channels" in some way, but this leaves room for interpretation. 1 input channel? 2 output channels? </p>