1 <?xml version="1.0" standalone="no"?>
3 <!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.4//EN" "http://www.oasis-open.org/docbook/xml/4.4/docbookx.dtd" [
7 <section id="sn-working-with-layers">
8 <title>Working with layers</title>
10 It is possible to arrange regions in a playlist (track) so that they
11 overlap - one starts before another finishes, for example. Because of
12 this, its important that there is a clear and understandable rule for
13 what you will hear when playing back these kinds of region arrangements.
17 Every region in a playlist is assigned to a layer. There can only ever
18 be one region on a given layer, although rearranging the playlist
19 (track) may change which region is on which layer. At any given point
20 along the timeline, you will hear the uppermost region at that point.
24 Of course, nothing in digital audio is ever quite that simple, and so
25 there are some complications:
28 <section id="layers-crossfades">
29 <title> Crossfades </title>
31 Whenever two regions overlap, there is the potential for a
32 <link linkend="sn-working-with-crossfades">crossfade</link> between
33 them. If the crossfade is not muted, then you will hear the contents
34 of the crossfade during the overlap, not just the uppermost region.
38 <section id="region-opacity">
39 <title> Region Opacity </title>
41 With a nod to image manipulation programs, Ardour allows you to
42 make regions transparent. By default, all regions are created opaque,
43 which means that when they are playing, no region below them are
44 audible. However, if you change the region to be transparent, the
45 region will be audible together with any regions below it. This
46 capability should probably not be abused; if you really want to mix
47 sounds together in this way, they should probably be on their own
48 tracks. Occasionally though, this can be a useful trick.
52 To change the opacity of a region, popup the region's editor,
53 accessible by context clicking on the region. Then click on the
54 "opaque" button, turning it on or off as desired.
58 <section id="choice-of-layering">
59 <title>Choice of layering</title>
62 There are two main decisions to be made with regard to how a playlist
68 Given overlapping regions, which order should they be layered in?
71 When should layering be changed?
75 <section id="layering-order">
76 <title>Layering Order</title>
78 Ardour provides three-and-a-half ways to decide on the order in which regions are layered. The most basic choice is:
84 <term>Most recently added regions are higher</term>
87 Regions which are later in time will be on higher layers.
93 <term>Most recently added or edited regions are higher</term>
96 Regions which were more recently edited or added to the playlist
97 will be on higher layers.
103 <term>Later regions are higher</term>
106 Regions which were more recently added to the playlist will be on higher
115 A new session has the layering style set to "Most recently edited or
116 added regions are higher". To change the layering style, open the
117 <emphasis>Session Properties</emphasis> dialogue and choose your layering
118 style from the "Misc" page. Changing the layering style only affects
119 future edits to the playlist; the existing layering of all playlists is
120 preserved when changing the layering mode.
124 <section id="modifying-layering-by-hand">
125 <title>Modifying Layering Explicitly</title>
127 If you want a particular region to be the uppermost when the current
128 layering style has put it on a lower layer, context click on the
129 region. Select the region from the menu that pops up, and in the
130 submenu that appears, choose one of "Move region to lowest layer" or
131 "Move region to upper layer". The layering for the playlist will be
132 recalculated to ensure that the region is on the layer you chose.
133 Note: these operations only have any effect if using one of the "Most
134 recently .." layer models.
138 You can see the precise layer a region is assigned in the popup region
139 editor, accessible by context clicking on the region.
144 At one time, Ardour offered more explicit control over the layering,
145 allowing you to move regions up or down to specific layers. This was
146 found to be problematic, confusing, and generally rendered
147 unnecessary by both of the layering styles the program now offers.
152 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude"
153 href="Some_Subsection.xml" />