2013-01-29 19:26:36 -05:00
|
|
|
|
2017-03-22 05:44:17 -04:00
|
|
|
<figure class="right">
|
|
|
|
<img src="/images/track-layer-dialog.png" alt="The Track layering menu">
|
|
|
|
<figcaption>
|
|
|
|
The Track layering menu
|
|
|
|
</figcaption>
|
|
|
|
</figure>
|
|
|
|
|
2014-02-05 12:32:01 -05:00
|
|
|
<p>
|
2017-03-22 05:44:17 -04:00
|
|
|
Ardour allows arbitrary <dfn>layering</dfn> of regions—there can any number
|
|
|
|
of regions at a given position. By default, the regions are
|
2014-02-05 12:32:01 -05:00
|
|
|
<dfn>overlaid</dfn> in the editor window, to save vertical space.
|
|
|
|
</p>
|
|
|
|
<p>
|
2017-02-25 00:30:29 -05:00
|
|
|
However, this display mode can be confusing for tracks with many overdubs,
|
|
|
|
because its not obvious in which order the overdubs are layered. Although
|
2014-02-05 12:32:01 -05:00
|
|
|
there are other methods of moving particular regions to the top of an
|
2017-03-22 05:44:17 -04:00
|
|
|
overlapping set, and although Ardour also has playlists to manage
|
|
|
|
<a href="@@playlist-usecases">takes</a> a bit more efficiently than just continually
|
|
|
|
layering, there are times when being able to clearly see all regions in a track
|
|
|
|
without any overlaps is reassuring and useful.
|
2014-02-05 12:32:01 -05:00
|
|
|
</p>
|
|
|
|
<p>
|
2018-06-23 07:24:51 -04:00
|
|
|
The example below shows a track with a rather drastic overdub situation,
|
2014-02-05 12:32:01 -05:00
|
|
|
viewed in normal <dfn>overlaid mode</dfn>:
|
|
|
|
</p>
|
2017-03-22 05:44:17 -04:00
|
|
|
<figure>
|
|
|
|
<img src="/images/overlaps_layered.png" alt="Overlapping regions in overlaid mode">
|
|
|
|
<figcaption>
|
|
|
|
Overlapping regions in <em>overlaid</em> mode
|
|
|
|
</figcaption>
|
|
|
|
</figure>
|
|
|
|
|
2014-02-05 12:32:01 -05:00
|
|
|
<p>
|
2017-03-22 05:44:17 -04:00
|
|
|
This display can be changed by <kbd class="mouse">right</kbd> clicking on the
|
|
|
|
track header, showing the menu displayed above. There are two choices for layers, and
|
|
|
|
<kbd class="menu">overlaid</kbd> is currently selected. Clicking on <kbd
|
|
|
|
class="menu">stacked</kbd>, the track display changes to:
|
|
|
|
|
|
|
|
<figure>
|
|
|
|
<img src="/images/layers_stacked.png" alt="Overlapping regions in stacked mode">
|
|
|
|
<figcaption>
|
|
|
|
Overlapping regions in <em>stacked</em> mode
|
|
|
|
</figcaption>
|
|
|
|
</figure>
|
|
|
|
|
2014-02-05 12:32:01 -05:00
|
|
|
<p>
|
2017-03-22 05:44:17 -04:00
|
|
|
Regions can still be moved around as usual, and can be dragged so that they overlay
|
2017-06-13 13:17:19 -04:00
|
|
|
each other again, but when the mouse button is released, things will flip back to them all being
|
2017-02-25 00:30:29 -05:00
|
|
|
stacked cleanly. The number of <dfn>lanes</dfn> for the track is determined by
|
|
|
|
the maximum number of regions existing in any one spot throughout
|
2017-06-13 13:17:19 -04:00
|
|
|
the track, so if a track has 10 overdubs stacked up in one spot,
|
2017-03-22 05:44:17 -04:00
|
|
|
it will end up with 10 lanes. Obviously, using a large track height
|
2014-02-05 12:32:01 -05:00
|
|
|
works much better for this than a small one.
|
|
|
|
</p>
|
2017-11-10 19:47:11 -05:00
|
|
|
|