Cue timing inconsistencies

[cblackley]

Mike- thanks for being open to tweaking

One thing I found confusing, and new students consistently have issues with in the Editor :
In most cue types ( Audio FIle etc.) the timing settings are similar.
But in a SFR you have to use " Time Override for Fades" which seems like a different thing, but is functionally the same as a "Fade in" or "Fade out" time.

Craig Blackley

[Mike Daniell]

The reason is that this field provides an optional override of an existing fade time. For example, suppose you have an audio file cue with a fade-out time of 3 seconds. You now set up an SFR cue to 'fade out and stop' that audio file cue. Here are some examples of what can be implemented:

• If the SFR cue has a 'blank 'time override for fades' then the audio file cue will fade out over 3 seconds.
• If the SFR cue has 2.5 in the 'time override for fades' then the audio file cue will fade out over 2.5 seconds,

If we called this SFR field 'Fade Time' (or 'Fade In Time' / 'Fade Out Time' depending on the action(s) selected) then this would imply this field always replaced the target cue's appropriate fade time, and if the SFR's cue's fade time field was left blank then that would be treated as 0.0 seconds, in line with other fade time fields.

[cblackley]

Aha ! I missed that it overroad existing fade times.
So a SFR uses the Fade Out time from the audio cue, regardless of where in the audio cue the SFR is triggered.
I always assumed the Fade Out time only applied when the audio cue ran all the way to the end of the cue.

Thanks for the clarification.

Craig Blackley