Congo control via Q-Lab

Which GO are you sending?

Is it the General MIDI Note On/Off for the GO button, MIDI Show Control "GO" or MIDI Show Control "GOTO CUE X"?

Midi Show Control GO

Basically the MSC GO calls the same function as when pressing GO. 

However, there are two different cases:

1. MSC GO with a cue number of 0: This is the same as pressing GO.

2. MSC GO with a non-zero cue number: This is the same as entering the cue number followed by GOTO.

Do both these variants have the problem?

I can imagine that GOTO case might behave slightly different.

Basically the MSC GO calls the same function as when pressing GO. 

However, there are two different cases:

1. MSC GO with a cue number of 0: This is the same as pressing GO.

2. MSC GO with a non-zero cue number: This is the same as entering the cue number followed by GOTO.

Do both these variants have the problem?

I can imagine that GOTO case might behave slightly different.

We are using Q-Lab to send a MSC Go with a cue number.  The cue fades correctly but if there is a delay on attribute times then the Q-Lab command seems to override them ie the delay times get ignored and the attribute times take the same time as the overall fade time.

I wonder if this is a side-effect of this being executed as a Goto (to jump to the correct cue before executing). If you send an MSC Go command with a cue number of 0, do the times get executed properly?