X-Git-Url: http://shamusworld.gotdns.org/cgi-bin/gitweb.cgi?a=blobdiff_plain;f=include%2Fpushpull-trimming.html;fp=include%2Fpushpull-trimming.html;h=eb02dbfd41a879d46947eca9ac51587511d19ef6;hb=2098e011e638b5c86c56e68df7757975fc4d728f;hp=0000000000000000000000000000000000000000;hpb=0e127ce41d7120d505f3aa9ae18dce679f403a3f;p=ardour-manual diff --git a/include/pushpull-trimming.html b/include/pushpull-trimming.html new file mode 100644 index 0000000..eb02dbf --- /dev/null +++ b/include/pushpull-trimming.html @@ -0,0 +1,37 @@ + +

+ Normally, when you trim regions by dragging with the mouse, it affects + only the selected regions. Their lengths are directly affected by the + trim operation, but nothing else is. Sometimes though, you might like + to trim a region that directly adjoins another, and keep this relationship + the same — you are not trying to make one of the regions extend + over the other — you would like the junction to move in one + direction or the other as part of the trim. This requires trimming both + regions on either side of the junction, in opposite directions. + Push/Pull trim, activated by pressing shift key before + starting the drag, will do just that. Here's a few pictures to show the + difference in the results of a normal trim and push/pull trim. First, + the initial situation: +

+region arrangement before trim +

+ Here is what happens after we trim the right hand (selected) region by + dragging its starting position earlier: +

+region arrangement after a trim +

+ You can see that it now overlaps the earlier region and a crossfade has + been created between them. +

+

+ Lets look now at what happens if we do the same trim, but Left-dragging to turn it into a push-pull trim instead: +

+region arrangement after a push trim +

+ There is no overlap, and the end of the earlier region has been moved + along with the start of the later region, so that they still directly + adjoin each other. +

+ +