diff options
Diffstat (limited to 'manual/xml/working_with_layers.xml')
| -rw-r--r-- | manual/xml/working_with_layers.xml | 112 |
1 files changed, 58 insertions, 54 deletions
diff --git a/manual/xml/working_with_layers.xml b/manual/xml/working_with_layers.xml index bd843ca305..7027064079 100644 --- a/manual/xml/working_with_layers.xml +++ b/manual/xml/working_with_layers.xml @@ -21,8 +21,8 @@ </para> <para> - Of course, nothing in digital audio is ever quite that simple, and so of - course there are some complications: + Of course, nothing in digital audio is ever quite that simple, and so + there are some complications: </para> <section id="layers-crossfades"> @@ -38,14 +38,14 @@ <section id="region-opacity"> <title> Region Opacity </title> <para> - In a perverse nod to image manipulation programs, Ardour allows you to + With a nod to image manipulation programs, Ardour allows you to make regions transparent. By default, all regions are created opaque, which means that when they are playing, no region below them are audible. However, if you change the region to be transparent, the region will be audible together with any regions below it. This - capability should probably not be abused - if you really want to mix - sounds together in this way, they should probably live in their own - tracks. Occasionally though, this can be useful trick. + capability should probably not be abused; if you really want to mix + sounds together in this way, they should probably be on their own + tracks. Occasionally though, this can be a useful trick. </para> <para> @@ -55,70 +55,74 @@ </para> </section> - <section id="layering-styles"> - <title> Layering Styles </title> - <para> - When you are recording new material for a track, its typical to want - to new material recorded "over" existing material in the track to be - what you hear on playback. For example, if you overdub part of a - guitar solo, you normally want the overdub to be audible, not hidden - by the old version that was already there. By contrast, when editing - using splitting/trimming/moving of regions to create a particular - arrangement along the timeline, many people find that they want - regions that start later on the timeline to be the ones that are - audible. - </para> + <section id="choice-of-layering"> + <title>Choice of layering</title> <para> - To facilitate these two contradictory desires, Ardour features three - different styles for assigning regions to layers. + There are two main decisions to be made with regard to how a playlist + should be layered: </para> <variablelist> - <title></title> - <varlistentry> - <term>Most recently added regions are higher</term> - <listitem> - <para> - Use this style when recording/overdubbing new material. Edits of - any kind do not modify the layering. - </para> - </listitem> - </varlistentry> - <varlistentry> - <term>Most recently added/moved/trimmed regions are higher</term> - <listitem> - <para> - Use this style when recording/overdubbing new material, but you - want basic edits to cause regions to rise to the top. - </para> - </listitem> + Given overlapping regions, which order should they be layered in? </varlistentry> - <varlistentry> - <term>Later regions are higher</term> - <listitem> - <para> - Use this style when rearranging and editing regions. - </para> - </listitem> + When should layering be changed? </varlistentry> </variablelist> + <section id="layering-order"> + <title>Layering Order</title> + <para> + Ardour provides three-and-a-half ways to decide on the order in which regions are layered. The most basic choice is: + </para> + + <variablelist> + <title></title> + <varlistentry> + <term>Most recently added regions are higher</term> + <listitem> + <para> + Regions which are later in time will be on higher layers. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Most recently added or edited regions are higher</term> + <listitem> + <para> + Regions which were more recently edited or added to the playlist + will be on higher layers. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term>Later regions are higher</term> + <listitem> + <para> + Regions which were more recently added to the playlist will be on higher + layers. + </para> + </listitem> + </varlistentry> + </variablelist> + </section> + <para> - A new session has the layering style set to "Most recently - added/moved/trimmed regions are higher". To change the layering style, - open the <emphasis>options editor</emphasis> and select the - "Layers&Fades" page. There is an option there to select the style - you want. Layering style may be changed at any time. The existing - layering of all playlists is not changed when changing the layering - model. + A new session has the layering style set to "Most recently edited or + added regions are higher". To change the layering style, open the + <emphasis>Session Properties</emphasis> dialogue and choose your layering + style from the "Misc" page. Changing the layering style only affects + future edits to the playlist; the existing layering of all playlists is + preserved when changing the layering mode. </para> </section> <section id="modifying-layering-by-hand"> - <title> Modifying Layering By Hand </title> + <title>Modifying Layering Explicitly</title> <para> If you want a particular region to be the uppermost when the current layering style has put it on a lower layer, context click on the |