Simultaneous cues on ETC Ion running EOS

[Txreilly]

Hello,

I am trying to write simultaneous running cues on an ETC Ion board and not getting anywhere. I tried to write a cue with just the cyc channels and have it run during the scene. Then I tried to write cues and select specific channels that did not include the cyc channels before recording the cues that would run while the cyc is still running. I is a long cue. I am doing something wrong. Will someone please veer me towards documentation or video that may be of help.

Also, I have not been on Control Booth in a while. This is my third attempt to post this question. When I type in the Thread title, the text box for the question goes away and I see a list of threads. I cannot figure how to get to the text box so I am just enter in the box first. My apologies if I am able to post the thread without a title.

Thank you,

 

[danTt]

What isn't working when you try what you tried?

 

[ChrisB_SanDiego]

Based on what your saying I can only make some guesses. It sounds like the cyc is stored in multiple places.

Some of the most common issues people have when dealing with multiple cues is the mode of the board: Cue Only vs Tracking

This is epecially problematic with multiple cue lists. If you aren't familiar, consider looking at the chapter 3 section of the proficient ETC training: https://www.etcconnect.com/Support/Tutorials/Eos-Family-Videos/Level-4-Proficient.aspx
If it's one cue stack, consider placing blocking. Chapter 7 https://www.etcconnect.com/EosFamilyVideos/Level-1/

What do you mean by "simultaneous running cues"? 1 cue stack, with multiple cues running? as in delay, follow cues, or parts? Or multiple cue lists?

Without more information, it's hard to narrow down

Depending on which version of EOS you are running. you can try the following:

• let's say your first cyc is channel 11.
• go into the first cue that has the expected look. hit [About] [11] [Enter]. It should tell you where that information is coming from (what cue, cue lists, sub, etc.).
• repeat for each cue until you have the wrong look, and that should tell you where the problem is starting.

 

[jglodeklights]

Let me know if I'm getting this correct- you have a single cue list that you've recorded a base scene look, and then you recorded a cyc change look that should take x number of minutes. In the meantime, you've started recording subsequent interior changes; say for actors moving around the scene. Yes? If so when you were recording new cues after the cyc change look has it been while the cyc change cue is still actively running? If you RECORD during the playback of a long cue you're going to record the cyc channels as well as your manual (red) level channels at whatever value they have progressed to. There are a few ways to go about not having this happen. The first is GO TO CUE (cyc starts its change) and record your new cues with the cyc already in its complete state. When you go back and run things from the cue where the cyc starts its long change it will playback correctly. You can fix your subsequent cues if you've already recorded from the cyc change to allow it to fade normally by going to the first change cue after the cyc move and @-ENTERing the cyc channels to bring back the levels from the cyc cue and doing an UPDATE THRU to update the information to each of the subsequent cues. What you'll want to see data wise is the cyc channels in Magenta color at what will be the finished look.

Finally, if you want to record while the cyc change cue is running, use RECORD ONLY to record new cues. RECORD ONLY stores only manual levels (red levels) so it won't capture the current state of all channels (which is what RECORD does).

 

[almorton]

Above is absolutely right, and will allow what you want. If you're recording the cues in order, whether you'e in tracking or cue only mode won't matter - it's only if you start recording cues out of order that this might trip you up, but you can go back fix things afterwards as @jglodeklights suggests.

 

[Txreilly]

Thank you, thank you, thank you! I got too busy during the show to play, but I just tried the instructions J provided to record cues and it worked flawlessly. J, you did understand what I was trying to do and didn't communicate too well. I will try editing cues next.

Sorry it took so long to get back to you all. I really appreciate all the recommendations and assistance!

 

[jtweigandt]

Coming to the party late.. but could you also make the cyc activity a very long timed effect that doesn't loop?

 

[almorton]

You  could but you don't need to. I've had shows where the cyc faded from the start of the show to the interval, and from the restart to the end as two continuous fades while all the other fades were going on without any need for effects, second cue stacks, macros or any other tricks. It just works. Oh, and in that particular case, the show was recorded in cue only mode, in case anyone tries to tell you that it can only work in tracking mode.

 

[jglodeklights]

Making this an effect if simply fading values over a long time seems to me to introduce an additional level of complexity in dealing with the data for this. Or duplicative data. For example if the cyc levels are fading completely out or to some transitional look that continues into the transition and there is need to ASSERT the values to rush the tail end of things (an ASSERT tag on a cue forces all values from the cue in time whether they are tracked or new). You may need to manage background values and effects in/out timing appropriately to ensure there is no blip when the effect is stopped on top of whatever data you store in the effect. You may need to update data in multiple places to make it work, and essentially end up with your stored cue data being the same as not operating this on an effect.

EOS as a Move/Fade console is designed to handle this design need without issue and without workarounds- only moves are actually played back with the G-O on each subsequent cue. It is why ETC decided to make the software work this way. It only requires knowledge of the proper way to store additional information. RECORD = the complete current state, RECORD ONLY = only manual information, UPDATE = modify already stored values with new manual information. People tend to forget about RECORD ONLY, but it's a REALLY REALLY REALLY useful tool. I can't stress enough that learning the proper times to use it will make your (or your designer's life) a lot easier.