From: Ed Ward Date: Mon, 19 Jun 2017 15:27:41 +0000 (+0200) Subject: Rephrasing, precisions & corrections about regions naming X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=21758255836d0adb0856c6dedfcaff0d00450b75;p=ardour-manual Rephrasing, precisions & corrections about regions naming --- diff --git a/include/region-naming.html b/include/region-naming.html index 253f713..d51836e 100644 --- a/include/region-naming.html +++ b/include/region-naming.html @@ -1,14 +1,9 @@ -

Region names are initially derived from either

+

Region names are initially derived from either:

-

- It appears that recorded regions are always named after the track, not the - active playlist in that track. -

Whole File Region Names

@@ -20,7 +15,7 @@

For recorded regions, 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 Didgeridoo, the first recorded whole file region for that playlist will be called Digderidoo-1. The next one will be Digeridoo-2 and so on. @@ -32,8 +27,8 @@

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 - that are derived from them. + Editor's region list where they act as an + organizing mechanism for regions that are derived from them.

Normal Region Names

@@ -49,16 +44,21 @@

Copied Region Names

- If you copy a region, it initially shares the same name as the original. - When you perform an operation modifies one of the copies, Ardour will - increment the version number on the particular copy that changed. + Duplicating or splitting a region creates new region(s) that + are based on the same original files. Hence, they share the same base name (in the + exemple above, Hang drum-1), but their version number will be incremented + each time. Duplicating Hang drum-1.4 by left + dragging it will create a new region called Hang drum-1.5. Splitting + Hang drum-1.5 by hitting the S key will remove the + Hang drum-1.5 region and create two shorter regions named + Hang drum-1.6 and Hang drum-1.7.

Renaming Regions

- You can rename a region at any time. Use the region context menu to - pop up the Rename dialog. The new name does not need to - have a version number in it (in fact, it probably should not). Ardour will add a - version number in the future if needed (e.g. if you copy or split the region). + Regions can be renamed at any time using the region context menu : + right click > name_of_the_region > Rename... . + The new name does not need to have a version number in it (in fact, it probably + should not). Ardour will add a version number in the future if needed (e.g. + if the region is copied or sliced).

- diff --git a/include/working-with-regions.html b/include/working-with-regions.html index d71f5f1..17ed01d 100644 --- a/include/working-with-regions.html +++ b/include/working-with-regions.html @@ -2,11 +2,14 @@

Working With Regions

- 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: + 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:

@@ -21,18 +24,30 @@

- There are other attributes as well, but they do not define the region. Things you should know about regions: + There are other attributes as well, but they do not define the + region. Things to know about regions:

Regions Are Cheap

- 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.

Regions Are Not 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 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). + 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).

-