automation copy & paste

Official support for: mutools.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Hello.. I have very recently begun playing around with MuLab and am wondering about the methods of copying & pasting within the automation track. Nothing really behaves how I would expect it to.

I come from using Reason 3 (yeah, pretty much all I've been using since it came out!), and there the automation blocks are distinctly broken up into note lengths. I can select a chunk of automation 1/16th of a note long, and copy and paste it for every successive 1/16th length for as long as I choose. In MuLab, I can't figure out how to take a specific, discreet block of automation and repeat it predictably.

The lasso doesn't seem to snap to the note grid (probably a setting I haven't found yet) and even when set to a particular note length, doesn't appear to select with consistency. Sometimes it selects part of a block, but not what I actually lassoed; upon trying again it will select something else, sometimes a part which was not even within the lasso range.

When I try to paste a part, it is next to impossible to get it to paste where and how I want. One time I pasted something 3 times in a row, and the third time it was a thinned out version of what it was the first two times. It seemed like the clipboard data changed somehow. If there is a logic to this, please explain it to me! I looked in the documentation and couldn't find anything.

Basically what I want to do, is take an EXACT selection of automation and be able to easily replicate it wherever I want on the automation track. Is this possible? Say I record event data from an improvised session, and determine X parameter sounds best at one particular, brief moment in the session.. how do I easily copy that automated bit to the rest of the sequence?

I'm using 4.5.1 32bit free version.

Post

Zeroth: "control events" and "automation" are separate concepts in MuLab. MIDI event data is handled differently from automation curves. Not sure if you're mixing the two here but worth pointing out.

So first, turn off snap to grid everywhere you can find it (sorry Jo...). It's in a few places. It could be confusing what you see when you hit paste, as the events will get snapped. (It'll have been snapped when recorded, too.)

Then make sure you've zoomed in close enough to see individual events rather than close clusters. You can check by looking in the Event List to see whether you're seeing everything. Of course, if there's a lot of control events going on, it's going to be crowded.

Once you're sure you have the data where you expect it, selecting should be fairly straight forward - but note that the lasso only needs to intersect an event to select it, it doesn't need to enclose it, which is why you need to be zoomed in close enough to see the gaps.

Hope that helps a bit.

Post

In this context I'm not entirely sure what is considered a "control event" vs "automation", so maybe I am mixing the two. I press record and click the note icon for "event capture" which seems like it is control event related. Then I fiddle with a parameter & data shows up on a track showing what I was doing with it, automating that parameter as the song plays through that part. So it seems like it's pretty straight forward automation, since it automates a parameter. But now I'm thinking it's being "controlled" by "events".

Ok I looked in the list editor (hadn't seen that before) and that definitely makes it a little more clear what's going on, and easier to edit for specific lengths and parameter values. I also noticed that you have to lasso the *beginning* of each event for it to be selected. Thanks. I'll probably be back with more questions :)

Post

i like note based automation management schemes! :love:

Post

pljones wrote:So first, turn off snap to grid everywhere you can find it (sorry Jo...). It's in a few places. It could be confusing what you see when you hit paste, as the events will get snapped. (It'll have been snapped when recorded, too.)
No the quantize for event recordings only works on notes. By the way i already changed the very default for that to Off, cfr the other topic. You guys convinced me.

About snapping editor actions: That's a good feature, but of course there are situations you don't want it so that's why it can be switched off with a single click.

Post

danceface wrote:In this context I'm not entirely sure what is considered a "control event" vs "automation", so maybe I am mixing the two.
Automation is drawn in using points/curves and doesn't exist in the Event List editor. An automation part needs its own track (automation parts don't appear to be have the option of having their target set). You'll have specifically chosen to add an automation track from the menu. If you didn't, you're working with control events. (These can control MIDI Controller values or control automation parameters but they're still control events. Automation only targets automation parameters.)

(Hm. At least, I think that's right...)

Post

> DiGiT < wrote:i like note based automation management schemes! :love:
Maybe you can use the multi-point envelope for that.

Post Reply

Return to “MuTools”