Cues in group not always firing

[Robyn Just Robyn]

I have an audio QLab file, with cues in Groups.  

Groups have anywhere between 2 and 20 cues within the group, with all the groups set to Timeline, so all the cues should fire at the same time.  (Not nested groups)

I seem to have a weird issue where sometimes I run the group, and all cues fire as expected without issue.  Then the next time I fire the group, only some of the cues within it fire..

I'm firing them via a midi link from a lighting desk.

Tonight I test ran my entire show file prior to the show and it worked without any issues.

Then without touching anything at all, I ran the show, and upon firing a large group several of the cues within it did not run.

And the cue to stop the group running also somehow failed to stop the cues that were running.

No cue numbers were missed on the lighting desk - you can't easily skip over them. 

Has anyone else had experience of this?

When I tested the cue stack after the show, once again it all just worked fine.

I'm a bit stuck..  No idea where to look for the issue.

[Chris Clark]

Not sure what kinds of cues you're using - audio, video, network, etc. You mention firing the groups off from the light desk, but didn't really mention what the cues are doing. I think the closest thing I've experienced is an issue with outgoing (from QLab)  MSC commands - I was trying to perform a "reset" of an X32 at the beginning of a show, and also with later cues where I needed to change mutes and levels of FX sends/returns, etc. I discovered that if you pile all of the MSC commands together as a single firing group at the same time, only random ones will actually make it through, and not always the same ones. I figured out that if they're all offset from the previous one by a tenth of a second using pre-waits and auto-continues, it works fine. We've since modified the setup to use network cues into the X32 instead, and I think that issue doesn't occur anymore, but I still run them the same way when I have a whole group of commands to push just because that's how I'm used to doing it.

I could be way off-base with your issue though. I don't necessarily think the method you're using to start the group fire is making a difference though, it's likely something weird happening within the group. Have you tried using the GO button/Spacebar to fire the groups without the lighting desk involved just to confirm if the issue persists?

[Paul]

That sounds like a MIDI data loss problem. You could try checking the logs or using a MIDI Monitor (like Protokol) to check what MIDI data  is actually being sent / received