GoTo Cue timing doesn't work on our desk. When using GoTo cue #, it follows the cue timing. So if the cue is a minute long, it takes a minute to goto cue... I also tried GoToCue#Time5, and it still uses the cue's time.
If you send a copy of your showfile to eos@etcconnect.com and tell me one of the cues that is playing back twice, I'll take a look at it. Also, are you running v1.2?
Thanks, I received the show. I think all of the cues that you are seeing fire twice are due to the automark feature that you have enabled. Anywhere that you have a channel fading intensity to zero, and the next cue brings it up again, the mark of the NI parameters happens after the intensities fade out. If the intensity fades out in 5 and then the NI's fade in 5, the playback times will countdown in 5, then start counting down from 5 again for the NI's. If the intensity is already at 0, then you will only get a single countdown from 5. Does this sound like what you are seeing?
We have been discussing changes to how we display the progress of a running cue, some of which you will see in 1.3. Perhaps we should put an indication in these disaplys that you are seeing the progress of the automark, not the recorded cue.
I think the gotocue not working may also be a similar problem. In 1.2 if you goto a cue before a marked cue, the intensities will fade out in goto cue time, then the marked parameters will fade in cue time (while dark). This has been changed in 1.3, so that, for a goto cue, the marked params don't wait for the intensity to go out, and all parameters fade in goto cue time. There is now a softkey that appears when you do a goto cue, that allows you to delay the marks until after the intensity reaches zero. If this is what you were seeing, then intensities would have been using the goto cue time, but NI's would sometimes not.
