OUT OF ORDER CUE

Thank you for reaching out!

• Are the things that happened on the Eos side consistent with what the logs say? I.e. it was actually cue 261 that fired?
• The wrong Midi messages don't seem to be additional messages, they seem to happen in the exact right moment but have the wrong content. Is that correct?
• Can you provide logfiles? Attach them to your reply (Insert > Image/video/file) or send to eos(dot)moderator(at)etcconnect(dot)com.
• Can you profide logs from the Qlab side? (https://qlab.app/docs/v5/general/qlab-preferences/)
• What's your Midi signal path?

Thank you for your reply

• Are the things that happened on the Eos side consistent with what the logs say? I.e. it was actually cue 261 that fired? Yes this is correct on the log it will say run out of cue 261 which actually triggered
• The wrong Midi messages don't seem to be additional messages, they seem to happen in the exact right moment but have the wrong content. Is that correct? No so the cue that run out of order was a manual go cue i.e when to GO is called the operator pushes the GO button and it jumps into another cue
• Can you provide logfiles? Attach them to your reply (Insert > Image/video/file) or send to eos(dot)moderator(at)etcconnect(dot)com. Have sent these to you
• Can you provide logs from the Qlab side? (https://qlab.app/docs/v5/general/qlab-preferences/) unfortunately these werent being logged
• What's your Midi signal path? Qlab Mac USB out to an interface and then midi out cable to ETC Ion

So we are having issues still when the cue fired activates the event list through macro to enable it then jumps to the end of timecode cue

So we are having issues still when the cue fired activates the event list through macro to enable it then jumps to the end of timecode cue

Since this seems to be somewhat reproducible on your end it would really help if you could reproduce this while the Qlab side is logging as well.