Wait Function (Please give it back)

Solved. Sorry. Found "Delay Time"

Please Ignore.

Excellent.  We gave this feature a different name from Obsession to avoid confusion.... everyone seems to understand the idea of "follow".  Delay also seemed to make sense.  

Wait was the term that confusing.  Some some desks wait stages action within the cue, and on others it creates an auto-follow.  So it seemed best to avoid the word "wait."  

Welcome to the forum!

a

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

As a side note / question for Anne on holding down the time key. Maybe its just me, but it drives me nuts that when I hold down time to look at discrete timing, when I release the button, it still enters time into the command line and I end up having to hit clear. Is there a way for the console to differentiate between trying to enter a time, versus looking at a time? So if the button is pressed for less than half a second, then the user wants to adjust the time, but if its held for longer than .5 seconds, on button up, it just goes back to the regular view?

Maybe this already exists and I am doing something wrong? Or I'm the only one it bothers.

Thanks,

Ben, you are working on Ion, yes?  This has been fixed in the next software release.   There are a number of buttons/actions on Ion that can either be command line functions or used to change states (such as pressing the encoder to access more parameter functions.  Pressing the encoder  is also how you post those parameters to the command llne).   Next release throws those command line entries away when it has become clear to the desk that was not your intent.

We've also made it easier to use the fader controls key, as that button will now latch until you enter a command clearly not related to fader controls functions.

Stand by!

:-)

a

That will make my macro list go down.  Whooooo.

Anne, On the eos the Timing button has some nice funtionality. Is there an implimintaion for this in the ION? I use macros for this now. Mostly for the LD at the RVI.

Ben, while Eos has two time buttons - one for command line actions and a second one associated with the display navigation keys for toggling the timing view and activating flexi - time, Ion has just one time button.  But that one button can be used in just the same ways as on Eos.

Does that help?

a

Yes it does. That is why I make the Timing buttone available on a button on the RVI. So that designers can use this function with out messing with, or putting Time in my command line. I was just not sure if there were situations that I as a programmer would get more functionality out of using timming as apposed to the time button on the ION. But it seams that you guys are addressing the issues that have been noted on the ION. Thank you for your tirless work and for listening to programmers and LD in the development of this desk.