Check to make sure the following... If both cue lists have the same parameters (ie: both cues only contain color for the same fixtures)...then sending a GO command on the second cue will release the first one.
I have run into this when trying to use a command key to "flash a color" on my entire rig. You need to make sure that the second cue you trigger does not have the same parameters in use as the first cue.
Example- cue A has only color values cue B has only color values cue C has color and beam values
If you trigger cue A...then trigger cue B...cue A will release. But, If you trigger cue C...then trigger cue B...cue C will not release
The example above are assuming that the cues have ALL the same fixtures in them. If you add fixtures to different cues, that will also cause cues to "hang"
The issue is happening when the main cue list is the only one running. When it first started I thought it was miss handling the release macro for the chase cue list but noticed last night that the one time it happened out of some 14 run throughs was when the main cue list was the only one running. I may go days with no issue then it might happen up to 3 times in a shift. The problem is so random I can not nail down what is causing it.
Hmmm, That sounds like a tricky one. Might be tough to diagnose without seeing it happen in person. Are you saying that you are running a single cue list that randomly releases itself (no cues outside that list are being triggered)? If so, that is VERY strange.
