ardour/manual
13
0
Fork 0
Code Pull Requests Releases Activity

more copy-editing of chapter 9.

Browse Source
This commit is contained in:
Jörn Nettingsmeier 2014-02-05 18:30:45 +01:00
parent e4978af65c
commit f95ce61050
2 changed files with 50 additions and 44 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -69,47 +69,3 @@ title: Playlist Operations
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 would like to apply two
different non-linear effects such as distortion or compression to the
same audio source (for linear effects, you could just apply them one after
the other in the same track).<br />
Create a new track, apply the original track's playlist, and
then apply effects to both tracks independently.
</p>
<p class="note">
The same result could be achieved by feeding your track to multiple busses which
then contain the processing, but this increases the overall latency,
complicates routing and uses more space in the Mixer window.
</p>
<h2>Using Playlists for "Takes"</h2>
<p>
Using Playlists for <dfn>takes</dfn> 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.
</p>
<p>
Each time you start a new take, create a new playlist with
<kbd class="menu">p &gt; New</kbd>
Later, you can Select your way back to previous or later takes as
desired.
</p>
<p>
If you want to record multiple takes and then "comp" between them, it
is probably better to simply record each successive take on top of the
others in "layers" and then edit them using the layer tools, explained
later.
</p>
<h2>Using Playlists for Multi-Language Productions</h2>
<p>
The same approach as for takes is useful when you are recording or
editing content in multiple versions, such as dubbed movie dialog in
several languages, and you want all versions on the same track, to
get the same processing. <br />
Select the appropriate language before exporting the session.
</p>

50
_manual/09_working-with-playlists/03_playlist_usecases.html Normal file
View File

@ -0,0 +1,50 @@
---
layout: default
title: Playlist Usecases
---
<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 would like to apply two
different non-linear effects such as distortion or compression to the
same audio source (for linear effects, you could just apply them one after
the other in the same track).<br />
Create a new track, apply the original track's playlist, and
then apply effects to both tracks independently.
</p>
<p class="note">
The same result could be achieved by feeding your track to multiple busses which
then contain the processing, but this increases the overall latency,
complicates routing and uses more space in the Mixer window.
</p>
<h2>Using Playlists for "Takes"</h2>
<p>
Using Playlists for <dfn>takes</dfn> is a good solution if you are going
to need the ability to edit individual takes, and select between them.
</p>
<p>
Each time you start a new take, create a new playlist with
<kbd class="menu">p &gt; New</kbd>
Later, you can Select your way back to previous or later takes as
desired.
</p>
<p>
If you want to create a composite edit from multiple takes, create a new
track to assemble the final version, and "cherry pick" from the playlists
in the original track by copying regions over as required.<br />
Alternatively, record each successive take on top of the
others in "layers" and then edit them using the layer tools, explained
later.
</p>
<h2>Using Playlists for Multi-Language Productions</h2>
<p>
The same approach as for takes is useful when you are recording or
editing content in multiple versions, such as dubbed movie dialog in
several languages, and you want all versions on the same track, to
get the same processing. <br />
Select the appropriate language before exporting the session.
</p>