Automated Fixtures Moving light pre show check

[lj274mvp]

Im doing a show with a bunch of moving lights,
I was just wondering what everyone else generally does for a ML check during pre show?
Currently I usually write a list of q's that step through every gobo/color wheel/ parameters - i.e gobo/color 1 time 1 follow 3 then switched to next gobo/color etc.
This list of cues can become very long with ML's that have a lot of gobo/color wheel or other parameters.
Am I doing this check correctly? or is there some other way that I can make it more efficiently so I'm not writing 50q's just for a moving light check?

thanks

 

[cbrandt]

I generally just do a lamp check and a control check (wiggle each one around a bit to make sure they move). I do a lot of one offs and short run shows, and my shop checks through all the parameters so I generally don't worry much about other things. For longer runs I'll just go through my palettes to make sure everything hits the mark, and that's a quick check of the parameters that I'm using for the show as well.

 

[sk8rsdad]

My ML check is much simpler than yours. I do a lamp on, a fixture reset, then check that I'm getting light out of the instrument and that the focus point hasn't drifted. If I have a finicky instrument I might add additional checks to make sure the troublesome bit is working as expected.

There is little point in checking things that cannot be remedied before the house opens. At some point your decision becomes one of pulling the unit out of service and either swapping or working around the absence of the fixture for that performance.

 

[bcronenwett]

Yup, I agree with the others. Lamp on, check to see if they came on and a global reset. Sometimes I'll run a few cues if a mover seem like it's acting up. I do a lot of corporate AV so like cbrandt the bench tech checks all the parameters after a show.

 

[JDurnford2011]

Lamp check to make sure they are on. I do this by selecting the highlight key if its available and step through the fixtures one by one and then make sure they pan and tilt.

If anything becomes wrong in a show, I just reset the fixture and that fixes the problem most of the time and you can usually do this without anyone noticing.

Thats a good idea though to write a cuelist of all the effects and what not but your right as it would take a little bit to go through all of them. It depends on how much time you have to do it I guess. Generally though a quick check is easiest and quite reliable.

Justin Durnford
Lighting Specialist

 

[bishopthomas]

Lamp on and locate. Then I'll start programming. If you're talking about a preprogrammed show and you're just wanting to make sure everything is working then just go through it all. Color wheel(s), gobo(s), zoom, prism, focus, etc. Just a quick run through. Do it with all of the lights of one model selected then move on to the next group.

 

[lj274mvp]

ok so it seems basic general consensus is, its not really that important to check every single parameter of a moving light. But maybe check only the parameters/pallets/focus points used in the show?

I forgot to mention, my first Ml check Q is all the movers global reset one by one then when that is done they all lamp on. Then all movers at a focus point that is down center stage with the iris at minimum basically making sure pan/tilt/iris/intensity work.
Do you think if the movers are correct in this Q its safe to assume they will be fine for the show? i.e the other focus pts/pallets will be fine?

 

[rochem]

My preshow checks are usually a little more involved than some of the things mentioned here. I won't step through every gobo, for example, but I will check every gobo wheel for functionality - making sure I can change gobos, rotate them, etc. It depends on what parameters I'm using in that show - if I never have a gobo rotation, I won't bother to check that. It's not too uncommon for one color mixing wheel to get stuck, and you wouldn't notice that unless you test each color flag in your preshow. Often these problems can be fixed with another reset, but if you didn't do the check, you wouldn't know that until it's too late. I can't imagine not checking each parameter you're using - a stuck color wheel or gobo wheel could completely ruin a scene, and potentially get you fired if it was something simple that you should have seen. For most shows I work, I am called at hour before half hour (90 minutes to curtain), which gives me plenty of time to swap out a defective unit so I can look at it on the bench.

As a programmer, I check EVERY parameter at the beginning of every day, no exceptions. Even when the Head Electrician has already powered up and tested the rig, I still check every parameter just to satisfy myself. At the end of the day, I'm the one who will have to tell the LD that we can't do what he wants right now because of a maintenance issue, and no one wants to be that guy.

As for a single Reference cue, this is pretty standard. I don't like to use Downstage Center as I usually have a fixture hanging right there, and that doesn't tell me anything. I usually choose a point around midstage left, sometimes on a scenic wall if scenery exists, in a place where the maximum number of fixtures have to move as far away from their home position as possible. However, if I have a very specific special on something that I can check (like focused on scenery, or if an actress comes out to do her routine every night as part of her warmup), I like to check this as well just to be extra safe.

 

[lj274mvp]

Thanks Rochem.
so basically what your saying for preshow check on a show that is frozen and currently running is have a Q that goes from gobo 1 to the last gobo on the wheel? and the same for color rather than stoping for x amount of time on each and every gobo/color?

 

[rochem]

Depends on the show. For tours, I've programmed long, complicated cue stacks that step through everything parameter individually, with lots of autofollows, then repeat themselves over and over. But if I'm also the board op, or if it's not a very long running show, I'll usually just check everything manually. If you have a good view of the stage from the console, it only takes a few minutes to step through every parameter to ensure it's functioning properly. I've also been known to program a "Dance Party" cue as part of the ML checkout - essentially, every ML running a ton of effects bouncing through pretty much every parameter. It's the worst flash and trash you've ever seen, but it makes the props department's sweeping and mopping duties a little more fun.

Thanks Rochem.
so basically what your saying for preshow check on a show that is frozen and currently running is have a Q that goes from gobo 1 to the last gobo on the wheel? and the same for color rather than stoping for x amount of time on each and every gobo/color?

 

[PeteEngel]

You may want to consider a staggered lamp ignition sequence, depending upon the size of your system. If all of your fixtures strike at the same time you have a pretty significant draw on your electrical service, even if for a short time. If some fixtures do not strike the first time, this could be the cause (not that this was the initial question...).

 

[shiben]

Depends on the show. For tours, I've programmed long, complicated cue stacks that step through everything parameter individually, with lots of autofollows, then repeat themselves over and over. But if I'm also the board op, or if it's not a very long running show, I'll usually just check everything manually. If you have a good view of the stage from the console, it only takes a few minutes to step through every parameter to ensure it's functioning properly. I've also been known to program a "Dance Party" cue as part of the ML checkout - essentially, every ML running a ton of effects bouncing through pretty much every parameter. It's the worst flash and trash you've ever seen, but it makes the props department's sweeping and mopping duties a little more fun.

This is what I usually do. On the last show I did, I had all the MLs lamp on, move to center center, iris in, start a color roll, iris out, frost in, frost out, gobo roll, strobe, yellow flag in, cyan flag in, magenta flag in, sweep to their last focus point, then home and shutter. Worked great, and tested all the relevant parameters in about a minute.

 

[ProgrammerInTraining]

last show I did with over 500 movers the programmer had a burn out check que where the lights would run through most of its parameters and all us techs would keep an eye out for any odd balls before yhe show started

 

[kpnac]

This has been a great read. Just got our first ML in our renovated Auditorium. Some very useful info in this thread. Thanks

 

[lj274mvp]

You may want to consider a staggered lamp ignition sequence, depending upon the size of your system. If all of your fixtures strike at the same time you have a pretty significant draw on your electrical service, even if for a short time. If some fixtures do not strike the first time, this could be the cause (not that this was the initial question...).

I do stager the lamp strikes, its a simple macro that strikes a lamp waits 10 strikes the next and it just loops for some time going through all of them.

 

[agbobeck]

Hi all,

Just wanted to get the board's consensus on channel check and channel check with movers. first how do y'all channel check a conventional rig. I have worked in place where they use a channel check macro to go fixture by fixture, and I have worked places where they write a cue list and go group by group.

Also specifically with movers, how do you run through all the functions. Is there a way for the console to trigger the movers "test mode"? or do you have to write out a cue with each parameter.

Thanks for your ideas.

-AGB

 

[derekleffew]

For conventionals, see the thread http://www.controlbooth.com/threads/dimmer-lamp-check.7628/ .

 

[Erik456]

I personally test all features of my moving lights, by type, each and every show. Even if its a two show day, test before each show. I have a separate cue list of each type of moving light (right now its 4: Mac Vipers, VL3500S, VL2500W and VL500W) and it bumps thru each parameter while an electrician watches from the deck. Like mentioned above, you might not realize something is array (i.e.: bad strobe blade, shutter blade, bad gobo bulkhead but stuck in open, ect...) until you test it. I have the belief that if someone is paying to come see our show, they deserve 100% from us.