Show Cue System

Maybe things have always been this way and I've just never programmed a cue like this until now, but I'm pretty sure I have.

I've got a series of 4 manual cues, each one triggering an 8-10 second file of walking pedestrians and a passing car (they indicate brief transitions within a scene). Triggering the last of the 4 cues also triggers a file with the sound of distant fire engine sirens (as a standard cue with auto-start 0 seconds after start of the last passing car cue). Now the last passing car cue runs about 10 seconds and the fire siren cue runs about 30 seconds. But, for some reason, the fire siren cue has been ending when the passing car cues ends: after 10 seconds. Is this normal behavious for an auto-start cue?

If it isn't, then anybody have thoughts as to what's going on? This was happening with 10.2 and is still happening with 10.3.

If this is normal behvaiour, then I'd love to see a selectable option like: "Do not link to master cue's run-time", so it can be disabled.

(Yes, I know I could do this by triggering the fire sirens as a sub-cue of the last passing car cue, but I really like to have my triggered cues (which are highlighed and numbered in our scripts) be standard cues so I can see them easily in the cue list. Sub-cues have no Cue #s and are hidden unless you open the sub-cue list. I'd really like to be able to just see everything on my screen at a glance.)

-N

Sounds like a bug, as if the fire siren cue is being 'linked' to the last passing car cue. It shouldn't be since the cues are different lengths. I'll check this out, but meanwhile a solution would be to change the auto-start time from 0.00 seconds to, say, 0.01 seconds after the start. This should prevent the cues being 'linked'.

Thanks for the quick response, Michael!

Unfortunately, I've tried changing the auto-start time, but it still cuts off the fire sirens. I even tried it using auto-start BEFORE the end of the passing car file and it still cuts it off. I've since programmed other cues in the same fashion and they, too, get cut off.

I can send you the .scs file, if that will help.

-N

Yes, please email me the .scs file and tell me which cues you are referring to.

Fix ready for 10.3.1.

Thanks, Mike! Quick response, solid solution!

I have run into this problem as well on Version 10.2 and have a partial fix (if you are still running 10.2). For example say Q2 (Duration 30 secs) auto starts 0.00 secs after Q1 (Duration 10 secs) and Q2 stops on completion of Q1. Since the stopping seems to be linked to the first cue of shorter duration, re-order the cues. That is auto start the 10 second duration cue 0.00 seconds after the 30 second cue. Worked for me.