gotoCue will try to avoid open moves, so it will fadeout first, that's the first gotoCue time. and after channels that have faded out are out, they will do their move, that's the second gotoCue time
I prefer the old obsession way, where it ignores that. That is what Go-to-cue should be for me and why I use that. If I want to take care of open moves I would use Load-Cue.
Just to be clear. All your intensities will fade in the regular time. It won't fade lights out that are up in both cues. The marking you are seeing after the fade is just lights that would have been moving while they faded out. It does not extend the visible time of the cue it only makes it as "clean" as possible. It doesn't mark lights that are coming up in intensity unless you use the "Marks" softkey. It doesn't delay the up time on any intensities.
Thank you! I checked it on Stage. I saw everything happen in my default time. Just in Go-to-Cue- out i hear movements after that time. Now I understand...
when you say "time set" which time do you refer to? to the cue time? that's on purpose. GoToCue uses a default time from setup (setup, desk, manual control, GoToCue Time). if you want to use cue timing type GoToCue # Time Enter, this will take the cue time. if you want to take another time, use GoToCue # Time 8 Enter.
console in cue 0 , if i jump to cue 8 cue 8 has a up and down time of 3 but when you go to cue 8 enter they pop on with no time. If I then go go to cue 9 enter cue 9 pop with no time. I know i can do go to cue 9 time 3 and that will work, but should the board use the Cue list timing when you GO TO CUE #
Show setting cue setting all set to 3
Desk Settings manual control all times are set to 3..
No, the console should not take cue timing when GotoCue is used. It should and does use GotoCue timing.
Manual timing is used when you add manual values to a parameter (stuff written in red).
You were almost in the right spot for GotoCue time. Look further to the right, there is a box that says "GoTo Cue Time".
By the way default for that time is 5, someone seems to have changed it to 0 in your showfile...
