There is now no split editor/mixer ordering. Attempt to explain ordering of new track...

[ardour-manual] / _manual / 09_working-with-playlists / 01_understanding-playlists.html

diff --git a/_manual/09_working-with-playlists/01_understanding-playlists.html b/_manual/09_working-with-playlists/01_understanding-playlists.html
index 66eae3c9b991d1d40ad12d2984022a47c3a70d9e..87f1589bf9cac3df6903387d901088d332f6ae47 100644 (file)
--- a/_manual/09_working-with-playlists/01_understanding-playlists.html
+++ b/_manual/09_working-with-playlists/01_understanding-playlists.html
@@ -11,7 +11,7 @@ title: Understanding Playlists
 
 <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 <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>
+<p>If you have some experience of other <abbr title="Digital Audio Workstations">DAWs</abbr>, 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 plugins that require extra CPU time. If a playlist is not in use, it occupies a small amount of memory, and nothing more.</p>