Hog 1000 help. phone help, any help please!

Hello. I am a new user to the Hog 1000 and am having some issues. I have taken over a board with a bunch of preset things in menu banks etc, some preset groups and palettes. I have read the manual several times but am still having issues with a few things. Apparently my bosses do not want me to repatch any lights as they have things set in a way that works for them. I have three main questions.

First off: I have a 2 cue sequence on fader 1 that seems to work fine. Its just a wash with conventional lights, four mac 500's with yellow gobos projecting at the 12, 3, 6, 9 oclock postions( I'm working in a theatre in the round). When I pull down fader 1 and slide up fader 2 the yellow gobos are still there even though I have pressed play on fader 2 to start the cuelist. They do go away when I get to cue 2 on fader 2 but I think they shouldn't even be coming up in the first place. I'm thinking this is a tracking issue, or is it something I am doing or not doing within the programmer?( I may be wrong) but cannot figue out why the 500's appear to be ghosting those gobos over the 2nd fader.

My second issue has to do with grabbing fixtures and creating a group. First off there is a group labeled "all 500's", which when accesed pulls up all six of our Mac 500's. Some of the macs come up in an open white with gobos and 2 or 3 come up in purple. I want to know how I can set all 6 mac's to have the same ICFB parameters. I have tried to grab all fixtures and set all parameters for ICFB, then record that into my group labeled "all 500's" but it is not working.

Finally, we have 6 Clay Paky Stagelight 300's that seem to be stuck in strobe mode. I grab all fixtures, set intensity to full, and see them start doing a bad bally/strobe effect. When I pig+beam the only feature I can access is intensity level on the encoder wheels. No pan, tilt, colours etc. How do I get control of these things and get them to stop strobbing and pointing at the sky??

Any help will be appreciated. My job is on the line here as we have Mcoy Tyner coming in for a show on Saturday, which leaves me tomorrow to program and figure this out. Even better, if you are avaliable or willing to do help over the telephone, I'd gladly give you a call and maybe we can work on it that way. A HUGE THANK YOU in advance to anyone that can lend me a hand here.

Thanks- Phil
Parents
  • 0
    Hi Phil,

    1. The fader is only an intensity master, if you just pull down fader 1 but don't release the cuelist, then you've only taken out the intensity for those lights. You would need to release this fader for all of the attributes to be released. It is normal for you to see fader 2 take control of the attributes when you run cue 2 in fader 2 because it is asserting those values to fader 2 and "stomping" on them from fader 1.

    2. Groups only store a multiple fixture selection, not any attributes for them. You can make a position, color or beam pallete, that stores all of the lights attributes. Just press Use I, F, C or B to select what you want to put into a particular palette. By default a position palette only stores position info, etc.

    3. It sounds like you are using the wrong profile for these fixtures, since they are exhibitting this strange behaviour. Also is your patch correct?

    Hope this helps.

    Eric
Reply
  • 0
    Hi Phil,

    1. The fader is only an intensity master, if you just pull down fader 1 but don't release the cuelist, then you've only taken out the intensity for those lights. You would need to release this fader for all of the attributes to be released. It is normal for you to see fader 2 take control of the attributes when you run cue 2 in fader 2 because it is asserting those values to fader 2 and "stomping" on them from fader 1.

    2. Groups only store a multiple fixture selection, not any attributes for them. You can make a position, color or beam pallete, that stores all of the lights attributes. Just press Use I, F, C or B to select what you want to put into a particular palette. By default a position palette only stores position info, etc.

    3. It sounds like you are using the wrong profile for these fixtures, since they are exhibitting this strange behaviour. Also is your patch correct?

    Hope this helps.

    Eric
Children
No Data
Related

www.etcconnect.com