On Mon, 2002-12-16 at 11:26, simon.heath wrote: > Hi, just saw a question on CM forum about main automation. In the manual it > says this can be important but i don't understand what it is and am worried > I might be missing out on something crucial?? Depends on your approach to automation. Some people put all automation in a single pattern called "Main Automation" (or something similar). Personally, I find this approach to disorganised and prefer to put automation into individual/separate patterns labelled accordingly. (Tip: if you put something like "atm" at the end of every pattern name that contains automation, it can really help keep things organised and clear. I have wasted a lot of time looking through individual patterns trying to find which one is causing unwanted automation!!) The only exception to my rule is mix automation which I generally put in one pattern (since it runs for the length of the song and generally doesn't repeat itself in patterns). I'm even moving away from this convention to putting mix automation in separate patterns for sections of the song (verse, chorus, bridge etc). Some people call mix automation "main automation" btw. The reason I take this approach of separating automation is that often automation repeats itself in patterns (e.g. up/down filter sweeps or gating patterns for example), so its quicker to record or draw the automation once and set it to "play" in the required places. Some people put automation in the same pattern as the associated note data. This can simplify song arrangement if you _always_ want to play that pattern with the automation enabled. I generally don't take this approach - I prefer to layer two patterns together (one containing notes the other containing the automation) so that I can turn the automation on and off at will. Its probably easier to answer specific questions on automation if there is something that isn't clear. never the less, hope that helps a bit! Andy --