2017-02-25 00:30:29 -05:00
|
|
|
|
2014-02-05 05:19:59 -05:00
|
|
|
<p><dfn>Region names</dfn> are initially derived from either</p>
|
2013-01-29 19:26:36 -05:00
|
|
|
<ul>
|
2014-02-05 05:19:59 -05:00
|
|
|
<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 embedded/imported file they represent.</li>
|
2013-01-29 19:26:36 -05:00
|
|
|
</ul>
|
2014-02-05 05:19:59 -05:00
|
|
|
<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>
|
|
|
|
<p>
|
|
|
|
These are not audio files, but regions that represent the full extent of an
|
|
|
|
audio file. Every time a new recording is done, or a new file is imported
|
2017-02-25 00:30:29 -05:00
|
|
|
to the session, a new region is created that represents the <dfn>entire audio
|
|
|
|
file</dfn>. This region will have the name of the track/playlist/original file,
|
2014-02-05 05:19:59 -05:00
|
|
|
followed by a "-", then a number plus a dot and then a number.
|
|
|
|
</p>
|
|
|
|
<p>
|
2017-02-25 00:30:29 -05:00
|
|
|
For <dfn>recorded regions</dfn>, the number will increase each time a new recording
|
2014-02-05 05:19:59 -05:00
|
|
|
is made. So, for example, if there is a playlist called
|
2017-02-25 00:30:29 -05:00
|
|
|
<samp>Didgeridoo</samp>, the
|
2014-02-05 05:19:59 -05:00
|
|
|
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.
|
|
|
|
</p>
|
|
|
|
<p>
|
2017-02-25 00:30:29 -05:00
|
|
|
For <dfn>imported regions</dfn>, the region name will be based on the original file
|
2014-02-05 05:19:59 -05:00
|
|
|
name, but with any final suffix (e.g. ".wav" or ".aiff") removed.
|
|
|
|
</p>
|
|
|
|
<p>
|
2017-02-25 00:30:29 -05:00
|
|
|
Normally, whole file regions are not inserted into tracks or playlists,
|
|
|
|
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
|
2014-02-05 05:19:59 -05:00
|
|
|
that are derived from them.
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Normal Region Names</h2>
|
|
|
|
<p>
|
2017-02-25 00:30:29 -05:00
|
|
|
When a region is inserted into a track and playlist, its initial name will
|
|
|
|
end in a <dfn>version number</dfn>, such as <samp>.1</samp>. For a recorded region,
|
|
|
|
if the whole file region was <samp>Hang drum-1</samp>, then the region in
|
|
|
|
the track will appear with the name <samp>Hang drum-1.1</samp>. For an
|
|
|
|
imported region, if the whole file region was <samp>Bach:Invention3</samp>,
|
2014-02-05 05:19:59 -05:00
|
|
|
then the region in the track will appear with the name
|
|
|
|
<samp>Bach:Invention3.1</samp>.
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Copied Region Names</h2>
|
|
|
|
<p>
|
2017-02-25 00:30:29 -05:00
|
|
|
If you <dfn>copy a region</dfn>, it initially shares the same name as the original.
|
|
|
|
When you perform an operation modifies one of the copies, Ardour will
|
2014-02-05 05:19:59 -05:00
|
|
|
increment the version number on the particular copy that changed.
|
|
|
|
</p>
|
|
|
|
|
|
|
|
<h2>Renaming Regions</h2>
|
|
|
|
<p>
|
2017-02-25 00:30:29 -05:00
|
|
|
You can <dfn>rename a region</dfn> at any time. Use the region context menu to
|
|
|
|
pop up the <kbd class="menu">Rename</kbd> dialog. The new name does not need to
|
|
|
|
have a version number in it (in fact, it probably should not). Ardour will add a
|
2014-02-05 05:19:59 -05:00
|
|
|
version number in the future if needed (e.g. if you copy or split the region).
|
|
|
|
</p>
|
2017-02-13 14:53:37 -05:00
|
|
|
|