Cue Label bring up wrong label on slow network systems

This is a quirky set of circumstances, so probably isn't worrying anyone but me, but:

- Eos Ti as client connected to Master on the other side of the world via theBRIDGE

- As a resullt of that, round-trip time across network quite slow - 250-300ms

- Eos software v3.0.1

Generally this is all working fine. 

The weird quirk here is with labelling cues, particularly in blind.

Cue 123 LABEL sometimes puts the wrong cue label on the command line.

It's the label from shortened versions of the cue number - so in this case it could be the label from cue 1 or the label from cue 12 - ie. it feels like the 'label' is being processed by the client before it quite knows what the cue number is going to be. Sometimes you see the 'wrong' label appear on the command line then it gets replaced by the correct label. Sometimes the wrong label lands on the command line so if you don't notice and just press enter you apply the 'wrong' label to the cue number you specified.

This is almost certainly down to timing across the network and so is fine in most use cases, but I wonder if it's revealing that something odd is actually happening?

Thanks,

Rob.

Parents Reply
  • No, the two consoles are just a long way - 5500 miles - apart.

    Everything else works fine, so it just feels a bit odd that this oddity is there - the command line on the client is showing the correct cue number at the point I press 'label', so it's just interesting what hasn't caught itself up with what. Is the Client looking up the existing label, or does the master do that then send it to the command line?

    Rob.

Children
Related