Cues not playing - Getting "X"

[Sean Casey]

Hey everyone!

We have been using Qlab3 for some time now that we have a new projector at our theater. I've been learning a lot about it and it's a great program. One issue i've been having are cues not playing. This mainly happens after I've build all the cues out, save, then the computer goes to sleep or I come in the next day and open the workspace again i'm getting a red "X" on the cue and nothing plays. I usually have to rebuild the entire show in Qlab after this happens. 

Can anyone tell me why this might be happening? 

- Sean 

[luckydave]

On June 6, 2015 at 10:53:55 AM, Sean Casey (sean.an...@gmail.com) wrote:

One issue i've been having are cues not playing. This mainly happens after I've build all the cues out, save, then the computer goes to sleep or I come in the next day and open the workspace again i'm getting a red "X" on the cue and nothing plays.

When a cue is broken for any reason, QLab shows a red X in the leftmost column. Hover your mouse over a broken cue, and a tool tip will pop up telling you what's wrong. What does the tool tip say?

-- 
luckydave

[Andy Lang]

On Sat, Jun 6, 2015 at 1:53 PM Sean Casey sean.an...@gmail.com wrote:

 One issue i've been having are cues not playing. This mainly happens after I've build all the cues out, save, then the computer goes to sleep or I come in the next day and open the workspace again i'm getting a red "X" on the cue and nothing plays.

It’s important to never let the computer sleep when QLab is running, for various reasons. One of these, which is likely what you’re running into, is that QLab can only properly detect connected displays when it first launches. Unpredictable things, from surfaces breaking to crashes in some extreme cases, can happen if displays are changed while QLab is running.

Putting the computer to sleep effectively disconnects all of the displays, so should never be done while QLab is running.

Since your computer is set to sleep, it’s also worth checking to make sure your machine is fully optimized for show use. My teammate Sam posted a guide to important things to tweak on your computer for best performance in QLab, which you can find at http://figure53.com/notes/2013-10-29-prepare-execute-troubleshoot/

Have a great weekend!

-Andy

—
Andy Lang
@SoundGuyAndy
sup...@figure53.com

​

[micpool]

It's also worth saying that you almost never have to rebuild your entire show from scratch if you unexpectedly get a screen load of red x's. Once you have determined the cause of the problem by hovering the mouse as luckydave describes there is almost certainly then a quick fix that can get things up and running.  Usually  it's just a question of repatching a screen.    And if you do get a load of red Xs only save the workspace under a new name so you have a before and after save to work with.

Mic

[Chris Ashworth]

(Might also be that you need a license installed.)

-C

[micpool]

That would be the quickest fix of all!