manual/_manual/08_working-with-regions.html

32 lines
1.7 KiB
HTML
Raw Normal View History

2013-01-29 19:26:36 -05:00
---
layout: default
2013-01-31 12:18:42 -05:00
title: Working With Regions
2013-01-29 19:26:36 -05:00
---
2013-01-31 12:18:42 -05:00
<h2>Working With Regions</h2>
2013-01-29 19:26:36 -05:00
<p>Regions are the basic elements of editing and composing in Ardour. In most cases, a region represents a single contiguous section of one or more media files. Regions are defined by a fixed set of attributes:</p>
<ul>
<li>the source audio/MIDI file(s) they represent
</li>
<li>a starting point in the audio/MIDI file(s)
</li>
<li>a length
</li>
</ul>
<p>When placed into a playlist, they gain additional attributes:</p>
<ul>
<li> a position along the timeline</li>
<li> a layer</li>
</ul>
<p>There are other attributes as well, but they do not define the region. Things you should know about regions:</p>
<h3>Regions Are Cheap</h3>
2013-01-29 19:26:36 -05:00
<p>By themselves, regions consume very little of your computer's resources. Each region requires a small amount of memory, and represents a rather small amount of CPU work if placed into an active track. So, don't worry about creating regions whenever you need to.</p>
<h3>Regions Are Not Files</h3>
<p>Although a region can represent an entire audio file, they are never equivalent to an audio file. Most regions represent just parts of an audio file(s) on disk, and removing a region from a track has nothing to do with removing the audio file(s) from the disk (the Destroy operation, one of Ardour's few destructive operations, can affect this). Changing the length of a region has no effect on the audio file(s) on disk. Splitting and copying regions does not alter the audio file in anyway, nor does it create new audio files (only recording, and the Export, Bounce and Reverse operations create new audio files).</p>
2013-01-29 19:26:36 -05:00
{% children %}