Heya Mic. Hmm. Just tried this with various fade lengths. There's definitely some quirks:
Self killing Group Cue
eg, my video clip length is 8.3 seconds. With the Group Cue set to a 1 sec cross-fade, the Group Cue sums up the runtime to (8.3 x 2) - 2 = 14.6 secs. Loop works OK.
If the Group Cue cross-fade is increased, there's a possibility that the Group Cue length is less than the video clip length (8.3 x 2) - 5 = 6.6 secs.
In this case, the Group Cue kills itself without looping back to the top.
- Guardrail 1 - Make sure your Group Cue length is longer than the clip length by shortening the crossfade time. Or using a longer clip.
Where'd my fade go?
If the Fade Cue is relatively long, the Group Cue can loop back to the top and re-triggers the children video cues while the fade is still running. Seems OK for maybe 1/2 or 1 iteration, however multiple loops while fading and the Fade Cue loses track of the instances of the video cues to act on.
In this scenario the Fade Cue and Group cue have a bit of a fade-out / fade-in battle. Then once the Fade Cue runs out of time, it hard stops children video cues, and takes its bat and ball home. Poor outcome for everyone.
(I think that's why I started messing with a specific fade cue for each video cue & a stop cue for the group cue as I posted initially).
Also seems at what stage in the Group Cue loop that the Fade Cue is triggered has an effect. Could be the start of one child, with both, looping back to top, etc etc.
To fix this the fade cue should be relatively short. Perceptually 1 to 3 seconds seems to work.
So from my quick experimenting...
Guardrail 2 - Set the Fade Cue length & Group Cue cross-fade time to the same value. A couple of seconds for both seems robust.
PS My future self better appreciate this... :)