Why do 'as' and 'be' timers work differently?

[john-tapas]

Hi Mike

Is there a reason why the "After Start" and "Before End" Auto Start cues work in different ways?

"Before End" seems to trigger simply when the Main cue 'End' timer value is less than the value set in the auto start cue, whereas the "After Start" runs a separate timer. If you run the system in real time then there is no problem.

But when you are asked at a rehearsal to run the main cue from half way through, and all the "After Start" timed cues are thrown completely, it is a touch exasperating!

I now use BE wherever possible, although this is not possible in sub cues.

Clearly this is a complex issue since you have to decide what to do with any auto starts that have passed if you jump forward, BUT I would have thought the benefits would out way the drawbacks.

Perhaps I have missed something, being a relative newcomer to SCS.

Cheers

John

[Mike Daniell]

Is there a reason why the "After Start" and "Before End" Auto Start cues work in different ways?

Probably history. The "After Start" facility was included very early in the development of SCS, but "Before End" was added much later. "After Start" is implemented by changing the state of the cue to "Countdown to Start" when the controlling cue started, and thereafter the coutdown takes control without referring back to the controlling cue. When I implemented the "Before End" feature it didn't seem logical to change the state of the cue to "Countdown to Start" when the controlling cue started, but in hindsight it could have been implemented the same way. There are pros and cons in the two methods. I'll need to think thru ways in which the two could be modifed to provide the best of both.