• Date
    RobMerow
  • Date
  • Replies 1 reply
  • Subscribers 185 subscribers
  • Views 470 views
  • Users 0 members are here

Most "independantest" type of chase

In our theater we run a DMX hazer, which even at lowest output is too much for the space, so I have it programmed on a chase for 20 second haze, 20 second rest. It is very critical that this chase not be accidentally triggered by someone, as if the AC system is not on the correct setting we set off the fire alarm. Since we have a range of volunteers with their hands on the console, the risk of someone setting off the alarm is real.

Call me paranoid, but to eliminate the ability for someone to accidentally trigger or build the haze setting into a cue, I have the hazer running on a seperate, old unused console on its own universe (which obviously works).But we do have EOS, and my preference would be to have it run from the console. 

In short, what is the most secure, most independant way to program and run a looped chase that cannot possibly accidentally get recorded into a cue even if it is running at the time ithe cue is recorded?  Is there a way to also set the two control channels for the hazer as independant as well, so someone couldn't type 1 THRU 512 @ FULL and turn the thing on?

Parents

  • The first thing that comes to mind that satisfies ALL these, is to setup partitions and users.  Isolate the Hazer on a partition and user that is not the default for the desk. 

    You can then use a magic sheet with a command line object assigned to that other user.

    OR

    Run a macro that runs as User X to trigger the effect.

    HOWEVER

    The easier solution:

    If you only want to prevent them being recorded into cues or accidentally controlled via the keypad, then put the effect on a submaster that has Priority Shielded Enabled.  Then the only way that channel can be affected is by that Submaster (or another submaster controlling that channel, also with Priority Shield).  Priority Shielded makes the Sub (and its Channels) excluded from Recording, excluded from Manual control, and excluded from playback by any other container (again, except another Shielded Sub with the same channels).  The only thing that can override a Shielded Sub would be Parking that fixture on.

Reply

  • The first thing that comes to mind that satisfies ALL these, is to setup partitions and users.  Isolate the Hazer on a partition and user that is not the default for the desk. 

    You can then use a magic sheet with a command line object assigned to that other user.

    OR

    Run a macro that runs as User X to trigger the effect.

    HOWEVER

    The easier solution:

    If you only want to prevent them being recorded into cues or accidentally controlled via the keypad, then put the effect on a submaster that has Priority Shielded Enabled.  Then the only way that channel can be affected is by that Submaster (or another submaster controlling that channel, also with Priority Shield).  Priority Shielded makes the Sub (and its Channels) excluded from Recording, excluded from Manual control, and excluded from playback by any other container (again, except another Shielded Sub with the same channels).  The only thing that can override a Shielded Sub would be Parking that fixture on.

Children
No Data
Related

www.etcconnect.com