6 <p><dfn>Region names</dfn> are initially derived from either</p>
8 <li>the name of the playlist for which they were recorded,</li>
9 <li>the name of the track for which they were recorded, or</li>
10 <li>the name of the embedded/imported file they represent.</li>
13 It appears that recorded regions are always named after the track, not the
14 active playlist in that track.
17 <h2>Whole File Region Names</h2>
19 These are not audio files, but regions that represent the full extent of an
20 audio file. Every time a new recording is done, or a new file is imported
21 to the session, a new region is created that represents the <dfn>entire audio
22 file</dfn>. This region will have the name of the track/playlist/original file,
23 followed by a "-", then a number plus a dot and then a number.
26 For <dfn>recorded regions</dfn>, the number will increase each time a new recording
27 is made. So, for example, if there is a playlist called
28 <samp>Didgeridoo</samp>, the
29 first recorded whole file region for that playlist will be called
30 <samp>Digderidoo-1</samp>. The next one will be <samp>Digeridoo-2</samp> and so on.
33 For <dfn>imported regions</dfn>, the region name will be based on the original file
34 name, but with any final suffix (e.g. ".wav" or ".aiff") removed.
37 Normally, whole file regions are not inserted into tracks or playlists,
38 but regions derived from them are. The whole-file versions live in the
39 editor region list where they act as an organizing mechanism for regions
40 that are derived from them.
43 <h2>Normal Region Names</h2>
45 When a region is inserted into a track and playlist, its initial name will
46 end in a <dfn>version number</dfn>, such as <samp>.1</samp>. For a recorded region,
47 if the whole file region was <samp>Hang drum-1</samp>, then the region in
48 the track will appear with the name <samp>Hang drum-1.1</samp>. For an
49 imported region, if the whole file region was <samp>Bach:Invention3</samp>,
50 then the region in the track will appear with the name
51 <samp>Bach:Invention3.1</samp>.
54 <h2>Copied Region Names</h2>
56 If you <dfn>copy a region</dfn>, it initially shares the same name as the original.
57 When you perform an operation modifies one of the copies, Ardour will
58 increment the version number on the particular copy that changed.
61 <h2>Renaming Regions</h2>
63 You can <dfn>rename a region</dfn> at any time. Use the region context menu to
64 pop up the <kbd class="menu">Rename</kbd> dialog. The new name does not need to
65 have a version number in it (in fact, it probably should not). Ardour will add a
66 version number in the future if needed (e.g. if you copy or split the region).