Programing tips. Console conventions

I'm tooling around with the Martin m- pc software, but this question is broad enough to include all moving light consoles. What items do you leave in presets and what items do you use faders for... I am thinking that intensity is an obvious fader value, but are you splitting those faders up by fixture type, or ganging all fixture intensity on one fader.... I'm also using movement speed on a fader, but again, should I record it using all moving fixtures, or just fixture groups. If I use groups, I'm burning 3 faders for each group of movers. Can anyone comment as o how they set up their consoles. Thx
 
Re: Programing tips. Console conventions

Depends obviously on the size of the rig, but I think it's reasonable to do either an upstage/downstage split, or an odd/even, and create looks which include colour and beamshape and place them on two faders. Repeat for 2 faders for position combinations. Possibly you'd be better off, if you have PARs or LED colour wash, to keep the colours seperate from beamshape and make nice looking combinations.

That's coming from a HOG point of view anyway, hope that makes sense... :)
How many faders are you working with on your console?

David
 
Re: Programing tips. Console conventions

Hi David... it's martin M-pc, so 10 playback faders... I hoping to get into a M2GO console this year... so I'm learning the software first.
My largest show rig, is as follows
MArtin MAC 500 x 4 - Martin MAC 250 entour x 4 - Maritn Minimac profile x 4 - - Martin MAC 101 x 8
Blizzard Pro par 336 LED RGB x 18
12-24 par 64 1K on front truss. 4 x lekos

what I'll be running alot are the mac 101's and 4 x movers (depending on price of the gig is which mover and how many they get), and some loose LED pars.