Jump to content
Vari-Lite Controls Support Forum

Last cue of playback (chase) stays active


Recommended Posts

Posted

Hello.

 

We've set up playback 1 with 8 cues and converted it to a chase.

 

When the playback runs first time through, the cues run correctly.

 

However once cue 8 has run once, it stays active whilst cues 1-7 carry on running through the chase.

 

Any ideas what we're doing wrong?

 

The cues are a step chase of 8 segments of an RGB strip - Red1, then Red2, then Red3.... but once Red8 has lit, it stays lit whilst Red1, Red2, Red3... carry on stepping through.

 

Peter

Posted

Have the fixtures got an intensity or a virtual dimmer? If they don't, I wonder if move on dark is having an affect. Could you post the showfile?

Jon Hole
Global Product Manager, Systems and Control

Posted

configured with the generic 3Ch RGB fixture profile

I think it depends if you chose the RGB fixture with or without virtual dimmer. Send over the showfile and we'll take a look.

Jon Hole
Global Product Manager, Systems and Control

Posted

I saw this a while back with some LED lights I had. It could be that in the first step, tagged values at 0 do not get recorded into the step. To check, Load 1 MFF and see what is tagged there. Set the lights that are on in the last step of the chase to 0 (and tagged if you are set to record individual colours). Then Update the step.

 

It worked for me :)

 

Mike

Posted

Thanks for sending that over.

 

If you select fixture 113, press "colour" and then along the bottom of the touch screen tap "Red", "Green" and "Blue" so they all go light blue rather than dark blue.

 

Now, press and hold UPDATE. When the Update Window appears, tap "Smart Tag" to turn it off.

 

Now type "1" (for Cue 1) and press the {Playback 1 button} to update Cue 1 on that Playback.

 

This should solve this problem.

 

We've logged this as ZOS-7535 so this doesn't happen in the future

Jon Hole
Global Product Manager, Systems and Control

Posted

Thanks Jon.

 

We inadvertently 'fixed' this (read: 'avoided') this tonight before seeing your reply.

We updated some of the Home and Default values of the RGBs from 100 to 0 which resulted in this not appearing (as output) any more. It may well still be doing it in programming, but with intensity of 0 so not noticeable. :-)

 

Peter

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.