Wait Function (Please give it back)

Solved. Sorry. Found "Delay Time"

Please Ignore.

Great addition to the ION is the ability to apply times and delays specifically to a channel in a cue, instead of building an entire cue part for 1 channel.

On the current show I'm running, I have quite a few cues that have delays or separate times saved to specific channels.

[CHAN #] [DELAY] 2 ENTER
[CHAN #] [TIME] 2 ENTER

This adds a DELAY of 2 and a time of 2 to the channel # you specify.  These times, once stored, override the cue times.

If you haven't tried it, give it a shot!  I love it.

D

can you apply Delay times to channels on the EOS?

Since the software base for the EOS is the same as the ION, I would assume YES.  It should work exactly as I mentioned above.

[chan #] DELAY [length of delay required] ENTER

Just thought I'd point out that on Eos and Ion, these timing values can be entered in the same command.  They don't have to be entered as separate instructions.  It is also probably worth mentioning that when you hold the time key, to toggle the channel display to show discrete timing, the delay time is shown first, followed by the transition time.

:-)

a

I have alos found that the Flexichanel with Timing view to be helpful when dealing with discrete channel timing. You enter this state by pressing [Time] & [Flexi] at the same time. This will show channels that only have discrete channel timing in the current cue and leave other out. To get out of this flexi mode just press [Time] & [Flexi] again.

Thanks for the tip on Flexi w/ Timing, Ben.  Was unaware of it, but can't wait to use it.

On another, probably obvious point, that nonetheless threw me for a little while-  When you set/edit a cue's timing, it is automatically recorded.  With the discreet timing they become Manual data until the cue is updated.

Ben, the basic logic is that anything applied to a channel in live must be stored.  We make no assumptions about where you want to place that data.  Cue attributes, on the other hand, are automatically applied, as the target is quite clear.

a

Ben, the basic logic is that anything applied to a channel in live must be stored.  We make no assumptions about where you want to place that data.  Cue attributes, on the other hand, are automatically applied, as the target is quite clear.

a