Rephrasing, precisions & corrections about regions naming
This commit is contained in:
parent
ed98a49741
commit
2175825583
@ -1,14 +1,9 @@
|
|||||||
|
|
||||||
<p><dfn>Region names</dfn> are initially derived from either</p>
|
<p><dfn>Region names</dfn> are initially derived from either:</p>
|
||||||
<ul>
|
<ul>
|
||||||
<li>the name of the playlist for which they were recorded,</li>
|
|
||||||
<li>the name of the track for which they were recorded, or</li>
|
<li>the name of the track for which they were recorded, or</li>
|
||||||
<li>the name of the embedded/imported file they represent.</li>
|
<li>the name of the embedded/imported file they represent.</li>
|
||||||
</ul>
|
</ul>
|
||||||
<p class="fixme">
|
|
||||||
It appears that recorded regions are always named after the track, not the
|
|
||||||
active playlist in that track.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<h2>Whole File Region Names</h2>
|
<h2>Whole File Region Names</h2>
|
||||||
<p>
|
<p>
|
||||||
@ -20,7 +15,7 @@
|
|||||||
</p>
|
</p>
|
||||||
<p>
|
<p>
|
||||||
For <dfn>recorded regions</dfn>, the number will increase each time a new recording
|
For <dfn>recorded regions</dfn>, the number will increase each time a new recording
|
||||||
is made. So, for example, if there is a playlist called
|
is made. So, for example, if there is a track called
|
||||||
<samp>Didgeridoo</samp>, the
|
<samp>Didgeridoo</samp>, the
|
||||||
first recorded whole file region for that playlist will be called
|
first recorded whole file region for that playlist will be called
|
||||||
<samp>Digderidoo-1</samp>. The next one will be <samp>Digeridoo-2</samp> and so on.
|
<samp>Digderidoo-1</samp>. The next one will be <samp>Digeridoo-2</samp> and so on.
|
||||||
@ -32,8 +27,8 @@
|
|||||||
<p>
|
<p>
|
||||||
Normally, whole file regions are not inserted into tracks or playlists,
|
Normally, whole file regions are not inserted into tracks or playlists,
|
||||||
but regions derived from them are. The whole-file versions live in the
|
but regions derived from them are. The whole-file versions live in the
|
||||||
editor region list where they act as an organizing mechanism for regions
|
<a href="@@the-region-list">Editor's region list</a> where they act as an
|
||||||
that are derived from them.
|
organizing mechanism for regions that are derived from them.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<h2>Normal Region Names</h2>
|
<h2>Normal Region Names</h2>
|
||||||
@ -49,16 +44,21 @@
|
|||||||
|
|
||||||
<h2>Copied Region Names</h2>
|
<h2>Copied Region Names</h2>
|
||||||
<p>
|
<p>
|
||||||
If you <dfn>copy a region</dfn>, it initially shares the same name as the original.
|
Duplicating or splitting a region creates new region(s) that
|
||||||
When you perform an operation modifies one of the copies, Ardour will
|
are based on the same original files. Hence, they share the same base name (in the
|
||||||
increment the version number on the particular copy that changed.
|
exemple above, <samp>Hang drum-1</samp>), but their version number will be incremented
|
||||||
|
each time. Duplicating <samp>Hang drum-1.4</samp> by <kbd class="mod1 mouse">left</kbd>
|
||||||
|
dragging it will create a new region called <samp>Hang drum-1.5</samp>. Splitting
|
||||||
|
<samp>Hang drum-1.5</samp> by hitting the <kbd>S</kbd> key will remove the
|
||||||
|
<samp>Hang drum-1.5</samp> region and create two shorter regions named
|
||||||
|
<samp>Hang drum-1.6</samp> and <samp>Hang drum-1.7</samp>.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<h2>Renaming Regions</h2>
|
<h2>Renaming Regions</h2>
|
||||||
<p>
|
<p>
|
||||||
You can <dfn>rename a region</dfn> at any time. Use the region context menu to
|
Regions can be renamed at any time using the region context menu : <kbd class="menu">
|
||||||
pop up the <kbd class="menu">Rename</kbd> dialog. The new name does not need to
|
<kbd class="mouse">right</kbd> click > <em>name_of_the_region</em> > Rename... </kbd>.
|
||||||
have a version number in it (in fact, it probably should not). Ardour will add a
|
The new name does not need to have a version number in it (in fact, it probably
|
||||||
version number in the future if needed (e.g. if you copy or split the region).
|
should not). Ardour will add a version number in the future if needed (e.g.
|
||||||
|
if the region is copied or sliced).
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
|
@ -2,11 +2,14 @@
|
|||||||
<h2>Working With Regions</h2>
|
<h2>Working With Regions</h2>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
<dfn>Regions</dfn> 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:
|
<dfn>Regions</dfn> 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>
|
</p>
|
||||||
|
|
||||||
<ul>
|
<ul>
|
||||||
<li>the audio or <abbr title="Musical Instrument Digital Interface">MIDI</abbr> <dfn>source file(s)</dfn> they represent,</li>
|
<li>the audio or <abbr title="Musical Instrument Digital Interface">MIDI</abbr>
|
||||||
|
<dfn>source file(s)</dfn> they represent,</li>
|
||||||
<li>an <dfn>offset</dfn> (the "start point") in the audio or MIDI file(s), and</li>
|
<li>an <dfn>offset</dfn> (the "start point") in the audio or MIDI file(s), and</li>
|
||||||
<li>a <dfn>length</dfn>.</li>
|
<li>a <dfn>length</dfn>.</li>
|
||||||
</ul>
|
</ul>
|
||||||
@ -21,18 +24,30 @@
|
|||||||
</ul>
|
</ul>
|
||||||
|
|
||||||
<p>
|
<p>
|
||||||
There are other attributes as well, but they do not <em>define</em> the region. Things you should know about regions:
|
There are other attributes as well, but they do not <em>define</em> the
|
||||||
|
region. Things to know about regions:
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<h3>Regions Are Cheap</h3>
|
<h3>Regions Are Cheap</h3>
|
||||||
|
|
||||||
<p>
|
<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.
|
By themselves, regions consume very little in terms of 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, multiplying regions creation
|
||||||
|
whenever needed should not be much of an issue CPU wise.
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
<h3>Regions Are Not Files</h3>
|
<h3>Regions Are Not Files</h3>
|
||||||
|
|
||||||
<p>
|
<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 <kbd class="menu">Destroy</kbd> 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 <dfn>recording</dfn>, and the <kbd class="menu">Export</kbd>, <kbd class="menu">Bounce</kbd> and <kbd class="menu">Reverse</kbd> operations create new audio files).
|
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 <kbd class="menu">Destroy</kbd>
|
||||||
|
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 <dfn>recording</dfn>, and the <kbd
|
||||||
|
class="menu">Export</kbd>, <kbd class="menu">Bounce</kbd> and <kbd
|
||||||
|
class="menu">Reverse</kbd> operations create new audio files).
|
||||||
</p>
|
</p>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user