Show Cue System

I would like the ability to re-order the options under this tab. In my shows, cues tend to fade out more than they just stop without fading. Can I move that option to be first in order instead of second?

I tend to have a similar way of doing things to you Rick, but I find a quick and easy workaround is to create my first SFR subcue (FADE then STOP - all previous cues).
Copy it. (Ctrl-c)
Then simply paste it back everytime I put in a new cue: (Ctrl-v) - Bosh! Jobs a good'un.

I could add a Production Property for "Default Action for new SFR Cues" which you could set to "FADE OUT and then STOP", "STOP Immediately - do not fade out", or leave clear to allow SCS to use the existing logic. I wouldn't think any of the other SFR actions would be sensible as default settings for SFR cues.

Rick Wright wrote:I would like the ability to re-order the options under this tab. In my shows, cues tend to fade out more than they just stop without fading. Can I move that option to be first in order instead of second?

Make a SFR cue as normal and then give it a "Hot Key" Trigger (I normally use "0") and then you can fade out any playing cues at any point you want saves having to skip cues when going through your play list

HTH

PJ

Peter Jackson wrote:
Make a SFR cue as normal and then give it a "Hot Key" Trigger (I normally use "0") and then you can fade out any playing cues at any point you want saves having to skip cues when going through your play list

I do exactly the same (including "0"!). It does require you to have a standard overriding fade time which you will use for each cue. Optionally one could set up different hot keys with long and short fade times if necessary. Of course, a long fade can be built into the cue itself unless the running time of the cue is variable.

Malcolm

Mike Daniell wrote:I could add a Production Property for "Default Action for new SFR Cues" which you could set to "FADE OUT and then STOP", "STOP Immediately - do not fade out", or leave clear to allow SCS to use the existing logic. I wouldn't think any of the other SFR actions would be sensible as default settings for SFR cues.

That would work for me.

In the little theatres I work at, I usually set up SCS then an untrained volunteer runs the show. I like to set up SCS as a 1 button operation. "When you hear the cue, push the space bar." I don't want to tell them to hit a different key in the dark to trigger a fade. It's just that when I set up a SFR cue, the action I almost always want (fade out and stop) is 2nd in the list. If I could make it the default, it would save me a step.

I've been looking into this and found that the logic for determining the default SFR action is only applied when creating the SFR cue. It should also be applied on changing the selected cue, so I'd like to know if this change is really what's needed rather than establishing a new 'Default SFR Action' property or changing the order of the action entries.

The existing logic is as follows:

• On creating an SFR cue in the Editor, SCS initially populates the first line under 'Cue or Sub-Cue to be Actioned' with the last relevant cue that appears before the new SFR cue.
• SCS sets the corresponding 'Action Required' field to an action deemed to be the 'expected' action for that target cue. This action is determined as follows:
  • If the target cue contains a loop then the action is set to 'release from loop'
  • Else if the target cue contains a fade-out time then the action is set to 'fade out and stop'
  • Else the action is set to 'stop immediately'

If you then change the cue in that first line, the 'Action Required' is not recalculated, but it should be.

In SCS 11.4.0 this same process will occur if you change the 'Cue to be Actioned' in the first line of an SFR cue. For example, if you add an SFR cue and the 'Action Required' is set to 'Stop Immediately' (because of properties of the selected cue), and then you change the 'Cue to be Actioned' to a cue that contains a fade-out time (and no loop) then the 'Action Required' will be changed to 'Fade out and stop'. You can, of course, override the selected 'Action Required'.

Does the above provide the desired outcome?

That sounds good to me Mike