Not sure if I'm being dumb or if this is a bug.
The timing on my Cues doesn't add up correctly and I didn't see a bug report on it anywhere, so I feel as if I'm doing something dumb.
Two Part Q. Part 1 - Time=8 seconds . . . . Part 2 - Delay=8 / Time=1 . . . . . Total time of Q: 17 seconds.
Part 2 is supposed to wait until part 1 is done, then execute. (Which I believe it's doing.) but it's counting the 8 second delay in with the total time.
Part 20 has a mark flag on it. I'm presuming the lights that are marking in cue 58 part 20 are also coming down in intensity to 0% in that same cue part 1. As such those lights will fade down to 0% over 8 seconds, then delay for 8 seconds and then mark for 1 second. 8 + 8 + 1 = 17. Total Duration of Cue = 17 seconds.
but if I don't delay Part 20, it will execute when the GO is pressed. The 8 second fade of Part 1 & the 8 second delay of Part 20 should be concurrent.
I have Qs that work 'as expected' in the same show file:
Unless the channels have to fade out first before they can be marked
That unpredictability is frustrating. I get why, but I like knowing my Mark is delayed rather than trusting the software to be smart.