Okay, maybe a silly question. Most of my rock and roll experience is from the Whole Hog side of the world, but it means I've got my head stuck in the Hog method of programming movers. Most of my Frog experience is corporate events with a whole bunch of single-scene looks and effects, so maybe I'm going about this all wrong, can anyone check my logic?
WHEN USING THE HOG...
...especially for bands with a range of musical dynamics from soft to loud (like the one I'm touring with next month), I find it very useful to store the first submaster on each page as a "brightness-only" fader, and then to store all the rest of my cuelists like so:
FADER 1 - Mac250 Brightness
FADER 2 - Cuelist of Mac250 Positions
FADER 3 - Cuelist of Mac250 Effects
FADER 4+ - Conventional Groups
etc...
With Colour and Beamshape specified directly from palettes on the fly.
This gives me a whole lot of flexibility to custom-build my looks through any combination of attributes (IE, build the look or start the cue with the movers blacked out, then fade up the brightness to the desired level).
WHEN USING THE FROG...
...this is not going to be at all possible, even in Partial Mode, is it?
Am I correct that with the Frog, every step of every mover look and cuelist I build will have the brightness pre-built into it? Is there no way to seperate the brightness for the movers from the rest of their attributes, onto a seperate submaster?
I can absolutely work around this if so, it just means a different way of approaching programming *before* I start building a 20-page show.
Thanks again for all your input, it's been really helpful to get a 'gut check' from more experienced Frog trainers...