On a fine day, 28-04-2004, Geoff Kaiser wrote: >--- In logic-users@yahoogroups.com, Hendrik Jan Veenstra <h@k...> wrote: > >> What if you need dozens of such tempo changes? In such cases I'd >> like to be able to "copy & paste"... oh, wait, I forgot the 5/4 in >> bar 49... ah, lets just copy the 5/4 from bar 78 and paste it at >> 49... oh... screws up the timing of the other changes... Cool, now I >> can start all over again... >> > > You are forgiven -- and you _are_ missing something :). > >What am I missing? Either your way or my way it's going to be time >consuming. Your way is lots of cut/paste keyboard commands; my way >is a lot of mouse clicking. Keyboard is better, RSI-wise, than mouse. For me, that is... And I can copy/paste a lot faster than I can mouse-click-drag >Pardon me, but if you go back to add a time change early in the song >(say at "bar 49" in your example), how does that screw up the timing >of your other >subsequent time changes? Doing it thru the transport window >certainly doesn't screw up the other time changes here on my end. In >what way does it screw things up for you? It used to throw off the position of subsequent meter changes. Not sure if they fixed it in the meantime (a previous post in this thread suggested as much, but since I'm in the middle of refurbishing my house I can't check right now). But what used to happen was that when e.g. copy/pasting a meter change in bar 40, a subsequent 3/4 at bar 50, beat 1 suddenly ended up at something like bar 51, beat 3 (!). This has nothing to do with regions staying in place or anything like that. It truly was (and maybe is) a bug, reproducible and acknowledged by Emagic. >Perhaps you're talking about the fact that the *regions* stay where >they were while the bars and beats have shifted? No, of course not -- I'm not _completely_ retarded :-). -- Hendrik Jan Veenstra h @ k n o w a r e . n l Omega Art: http://www.omega-art.com/