Eos programming advice sought

[Genus]

Hi everyone,

 

I'm working on an Opera next month, and I would like to achieve a particular effect with regards the fading of the cyc.

 

For the duration of Act 2, I'd like to fade the LED batons I'm hiring for a cyc ground-row, through a variety of colours representing a sunset to finish with a night sky look on the cyc (which remains for Act 3). Now, this will be a sequence running over the whole 40 minutes of Act2. The effect is reproduced going the opposite direction, over a much shorter time (4 minutes) for the Entre'acte of Act 4.

 

Is there a direction you could point me as to how to achieve this on an Eos? I'm playing with the off-line editor, but I don't really know where to start. I was wondering if using two separate cue lists would work, with one dedicated to the cyc and leave the rest of the rig on the other.

 

Or whether running the whole thing through one stack will work, obviously I'll need other cues (affecting lamps on the stage) to run over the top at differing speeds during the Act and I don't want them to have any influence on the fading happening on the cyc.

 

Any advice gratefully received.

 

Many thanks,

 

Genus

[Joe Bleasdale]

Just make a cuelist that slowly advances through the sunset cues. Lookup follow cues in the manual and alter the timings to suit. The last shorter section is the same as the first just backwards with different timing... For example you copy cues 10 thru 1 to 11 thru 20 and alter the timing accordingly. You can put this on a separate fader and trigger it with a Macro from your main cuelist.

 

Hope this helps. Thanks.

[indyld]

Just to back up Joe's suggestion, I'd look to running this on a different cue stack on any desk where possible, and triggering it via a GO macro in the main stack. It makes editing of the transitions easier and more flexible, it's a bit like a stand alone show that runs in the background. The only thing that complicates this approach is if you have events in the main stack that need timing along with the cyc cues (although you can use additional macros, of course). Yes, this sounds like a case for a second stack and using follow ons.

[Tomo]

As you're wanting various shades of colour as you go along, the easiest and best will be to use a second cuelist.

(Overlapping fades Just Work, but you want more than one fade to create your sunrise/sunset)

 

Use "Execute" (softkey) links to hit go in the second cuelist at the appropriate moments in the main cuelist as follows:

 

Either be careful about cue numbers and link the cuelists (cue 1/1 fires cue 2/1, 1/5 fires 2/5 etc):

[Cue] 1/ {Execute} [Cue] 2/ [Enter]

 

Or manually insert Execute links for specific cues:

[Cue] 1/5 {Execute} [Cue] 2/7 [Enter]

 

When the main cuelist wants to take control of the cyc lights back from the secondary list (or vice versa), you may want to Assert that cue to override any ongoing moves and use the tracked values, or ensure there are moves recorded to take over.

 

Finally, take care when updating and recording the cyc lights to ensure that you're recording into the right cuelist.

 

Eos will normally update into the cuelist that currently has ownership of the channel (the one that last moved it), this works perfectly when channels are only used in one cuelist but once it's been used in more than one you may need to specify.

 

[Record] [Cue] 1/X [Enter] will record into cuelist 1 regardless of which cuelist currently owns them.

Selective store and Group Direct Selects will also help you a lot.