ION linking

So i'll try to give the picture:

Numerous cue lists placed on multiple faders.  Let's take cue list 1 on fader 1 as an example but they all do it.  Fader set as iMaster, HTP and Assert.

Cue 1/1 has a couple of colors and some gobos but all static. No movement.

Cue 1/2 has the same however colors switch fixtures.

Cue 1/3 now has one set of movers with a very slow rotating gobo.

Cue 1/4 has the same but more movers with a very slow rotating gob.

Speed of course doesn't really matter here.

Cue 1/4 is linked to 1 so that it can be tapped over and over and it will continue making changes.

I tap the bottom bump on fader 1 to set cue 1/1 then bring up the fader.  Cue 1/1 runs.  I then tap through the next 3 cues and all changes happen as recorded.

When it goes from cue 1/4 back to cue 1/1 everything changes to the cue 1/1 look but the gobos keep rotating.  If when in 1/1 the top bump is tapped it will send everything into white home then out.  When tapping the bottom bump back on again for cue 1/1 then it does what is supposed to do.

Only when tapping backwards from 4 to 3 to 2 to 1 or from 3 to 2 to 1 will cue 1/1 show as recorded.

Thoughts?

 

Parents Reply
  • If you don't have a gobo rotation setting stored in your first cue, the gobo will continue to rotate, even with an assert on it.  The assert function takes a tracked value and makes it behave like a move instruction on playback.  If the gobo rotation is not stored in the cue, it won't be impacted by the assert at all.  So you need to write the default gobo rotation value into your first cue to make the rotation stop.

    Hope that helps.

    a

     

Children
Related