X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fcorresponding-regions-selection.html;h=f94cb2546eef746f12a62d1195bafbc3d9eabea8;hb=081e7af0b6f6dec0ca685d3a538eacf20394c2cc;hp=811634e1f39bb9e41cfc0279add2677c3b0fd737;hpb=dfec6899ef2a121ccf2ff1d47008e7ac4844cf70;p=ardour-manual diff --git a/include/corresponding-regions-selection.html b/include/corresponding-regions-selection.html index 811634e..f94cb25 100644 --- a/include/corresponding-regions-selection.html +++ b/include/corresponding-regions-selection.html @@ -1,43 +1,43 @@ - +
- Track Groups have - a property titled Select which, if enabled, cause + Track Groups have + a property titled Select which, if enabled, cause Ardour to propagate a region selection in one track of a group to the corresponding regions of the other tracks in that group.
- For example, let's assume you have used multiple microphones to record a - drum kit to multiple tracks. You have created a track group, added all the - drum tracks, enabled the group and enabled the Select property for the group. - When you select a region in one of the drum tracks, Ardour will select the - corresponding region in every other drum track, which in turn means that a - subsequent edit operation will affect all the drum tracks together. + This can be particularly useful when an instrument has been recorded using + multiple microphones (e.g. a drum kit): by enabling the Select + property for the group, selecting a region in one of the tracks, Ardour will select + the corresponding region in every other track of the group, which in turn means + that a subsequent edit operation will affect all the tracks together.
- Regions in different tracks are considered to be corresponding for the purposes + Regions in different tracks are considered to be corresponding for the purposes of sharing selection if they satisfy all the following criteria:
- Sometimes, the rules outlined above are too strict to get Ardour to do what you - want. Regions may have been trimmed to slightly different lengths, or positioned - slightly differently, and this will cause Ardour to not select regions in other - grouped tracks.
+ Sometimes, the rules outlined above are too strict to get Ardour to consider regions + as corresponding. Regions may have been trimmed to slightly different lengths, + or positioned slightly differently, and this will cause Ardour to not select + regions in other grouped tracks. +- In this case, change + In this case, changing Edit > Preferences > Editor > Regions in active edit groups are edited together: to whenever they overlap in time. With this option enabled, r - egions in different tracks will be considered equivalent for the purposes of selection if they - overlap. This is much more flexible and will cover almost all of the + class="menu">whenever they overlap in time will allow regions in different + tracks to be considered equivalent for the purposes of selection if they + overlap. This is much more flexible and will cover almost all of the cases that the fixed rules above might make cumbersome.