X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fcorresponding-regions-selection.html;h=ff2025e4278467a767631d79d17b8aa5695b99b1;hb=7a4c28bd8605e90876ebee619de364ab7001e405;hp=cf0bdd42ba2e5aaa9134eb9824b3deb135aa04df;hpb=2098e011e638b5c86c56e68df7757975fc4d728f;p=ardour-manual diff --git a/include/corresponding-regions-selection.html b/include/corresponding-regions-selection.html index cf0bdd4..ff2025e 100644 --- a/include/corresponding-regions-selection.html +++ b/include/corresponding-regions-selection.html @@ -1,22 +1,22 @@ - +

- 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. + 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. + corresponding region in every other drum track, which in turn means that a + subsequent edit operation will affect all the drum tracks together.

How Ardour Decides Which Regions are "Corresponding"

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

    @@ -27,18 +27,17 @@

    Overlap Correspondence

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

    - In this case, change + In this case, change 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 + overlap. This is much more flexible and will cover almost all of the cases that the fixed rules above might make cumbersome.

    -