Unintended consequences with Chauvet Geyser RGB

Hey Nigel,

Since you're using Auto Marking with this, it is an all or nothing feature. Either everything will mark or nothing will mark, you cannot tell certain channels not to mark. If you were using Reference Marking then you would be able to do as Richard suggested. To turn Automark off for an individual cue, press [Cue x] {Automark Off} [Enter]. Note, that should happen in the actual cue where the fixture turns on, not in the cue where it marks.

I recommend putting the geyser at 01% in the previous cue, you shouldn't see any output (hopefully) and then in the next cue it will go to full like anticipated.

Hope that helps.

I have read the post. I'm using one in panto too. And decided that I would just put the smoke attibute onto a separate non-dim style channel.  So the smoke won't Mark for the next cue. 

I find a good way to mark a geyser is to make 2 cues that follow in zero count.

example

cue 1 marks

cue 2 triggers.

can be done with point (.) cues and am pretty sure it can be done with part cues but i have not personally tried it using parts....

the other way i dealt with marking smoke is to build an inhibition sub and use a macro to bring it up and down.   that

Lots of interesting ways of handling marking etc for a smoke cue in this thread.

As it happens we went with an entirely different solution, probably coloured by the fact that one of my co-stage managers is a software guy as his day job, and tends to do a lot of stuff as step based effects...

In general we are using the Geysers for a burst (approx 2 seconds) of smoke, with the LEDs ramping on over the first 0.5 seconds, holding for around 2 then ramping down.

We did this as 2 step based effects - one for the smoke, one for the intensity, applied to the separate components (ie Fog & Intensity) of the cue.  This is not "tampered" with by any of the marking.

  Nigel.

Lots of interesting ways of handling marking etc for a smoke cue in this thread.

As it happens we went with an entirely different solution, probably coloured by the fact that one of my co-stage managers is a software guy as his day job, and tends to do a lot of stuff as step based effects...

In general we are using the Geysers for a burst (approx 2 seconds) of smoke, with the LEDs ramping on over the first 0.5 seconds, holding for around 2 then ramping down.

We did this as 2 step based effects - one for the smoke, one for the intensity, applied to the separate components (ie Fog & Intensity) of the cue.  This is not "tampered" with by any of the marking.

  Nigel.

We can set a flag that fog/smoke parameters should be excluded from marking.  

Thoughts on that?

thanks,

a

My $0.02...

Having Mark behave differently depending on the fixture would be confusing.

FWIW, my preference is to run fog/smoke/haze on shielded subs and execute macros from cues to set levels of those subs.

sk8rs_dad said:

Having Mark behave differently depending on the fixture would be confusing.

It's not actually different for different fixtures, just that certain parameters wouldn't be marked. This is already done in some instances anyway so it's just extending that principle.

Dan

I think excluding smoke parameters from making would make sense. My personal favourite though would be to expose an individual auto mark on/off checkbox for each parameter in the Fixture profile editor... ;) 

i like the flag idea....we have all found creative ways to make smoke not mark.  it comes up when we use our LSG machine as well when i want the gas to run before the smoke starts. 

I would be for vote for Smoke not marking.  But I also love Uellriegg idea of a check box in the profile.  I have had problems getting hazers to not mark and had to resort to just making them basic dimmers to get what I wanted.