The Eos (and Ion) Forum

Re: Discrete Delay Weirdness

ldsfx — Sun, 28 Jun 2009 23:21:47 GMT

Ah, makes sense. Running final show right now, but good to know for the future. Thanks!

Re: Discrete Delay Weirdness

33boardop — Sun, 28 Jun 2009 23:09:36 GMT

Since you say you are using links, the question I have is whether 91 Thru 98 are moves or are tracking channels that are being asserted by the link function. If it's the latter, there are no moves to bind the timing info to. If you make them a block channel (redundant move) , you'll will have data to bind channel timing to.

Discrete Delay Weirdness

ldsfx — Sun, 28 Jun 2009 21:04:23 GMT

Day of 3 of a show and the set order has changed, so the designer wants to drop in links to bounce around the cue list, no problem. I believe there has already been a discussion about links not looking ahead to automark, but that;s another issue topic.

To get around what were now live scroller moves, I tried to simply delay the intensity on those channels, I typed

91 THRU 98 + 301 THRU 316 Intensity DELAY 6 ENTER and then updated the cue

(Since the fade was 6 already, this (i thought) would allow the scrollers to move in the cue fade, then the intensities would fade in after the 6 delay. However, after trying to clean up my tracks and execute this command multiple times, the desk would only stick the delay on Ch. 301-305.

Any Ideas?