QLab not playing cues

[Stephen Oakes]

Hi, I'm running QLab version 3.1.11 on a Mac Mini running OS X Yosemite Version 10.10.3

 

During a tech rehersal (thankfully) QLab stopped reponding to Go cues. I would be working fine, go to play the next track and nothing. Tried pressing the big GO button and still nothing. Tried to load it then play and still nothing. Was able to open the file and play it fine in iTunes. Was easy enough to fix simply by closing QLab and opening it up again.

 

Only has happened since the machine was upgraded to OS X Yosemite Version 10.10.3 and QLab version 3.1.11 (Both happened at the same time so not sure whats caused it?)

 

I ran the show on a different mac (It is running OS X Yosemite Version 10.10.2 and QLab 3.1.11) and it worked perfectly.

 

Is this the new upgraded version of Mac or is it a buggy version of QLab?

 

Thanks

Stephen

[Chris Ashworth]

Hi Stephen,

I’m afraid we don’t have enough information from your description to know the cause.  There is not a known issue that matches this description. 

We can take a look at your console logs for more clues, if you like. You can send those in from the Help menu —> “Contact Support” and check the console logs box.

Best,

Chris

[nizer]

This happened to me about 5 times during pre show tech setup. I quit and restart QLab and all is well. I have not changed my os. Space bar and go no longer function.

[Emer Värk]

I have same problem. 

QLab version 3.1.11 on a Mac Pro (3.5 GHz 6-Core Xeon E5) running OS X Yosemite Version 10.10.3

Lab shows the video clip but its not playing or not showing at all. Capture card with live video in works but background video don't. Problems started with OS X update. 

Another Mac Pro what is running 10.10 does not have this issue. Even its running more projectors. 

Can it be with pro video codecs update what was included in 10.10.3? Im running ProRes LT clips. Not that huge. 1024x544px.

Premiere in 5 days :(

emer...@gmail.com

[Emer Värk]

Same problem here. Video is triggering but not playing clip. Shows first frame on pause. 

Same time Intensity shuttle capture card works in same que. 

QLab version 3.1.11 on a Mac PRO (3.5GHz 6-Core) 16gb ram - OS X Yosemite Version 10.10.3

Activity monitor shows CPU running +600%

Maybe its connected to the pro codecs update?

Running video files on Prores lt. 

First time ever this kind of error. Premiere of the play in 5 days. 

Need help. 

Other Mac Pro with OS X 10.10 runs fine with 4 projectors connected. Must be OSx thing. 

Emer Värk

emer...@gmail.com

[Chris Ashworth]

Hi Emer,

First, welcome to the list; it’s nice to have you here. Sorry that you’re encountering troubles!

Second, I think whatever problem you have is quite different and unrelated to the (very vaguely described) problems other folks reported.

I say this only to encourage folks on the list to be precise about troubleshooting, as “it doesn’t work” applies to every problem, but doesn’t get us closer to solutions.

A few things to try in your specific case:

• Try using this beta build: http://figure53.com/temp/QLab-3.1.12-b9.zip
• Try a different codec
• Generally speaking, troubleshoot by changing one thing at a time and see if it helps. Keep trying different things (codecs, system configurations, etc)

If none of that helps, please write us at sup...@figure53.com and we can continue troubleshooting by collecting logs and such.

Best,

Chris

[Andy Lang]

Hi Emer,

In addition to the advice that my teammate Chris gave, one other thing to note is that we’ve sometimes seen similar symptoms of video cues not playing properly if displays are connected or disconnected while QLab is running, either intentionally or due to a bad cable or loose connection.

QLab can only properly scan for connected devices when it first launches, so it’s important to make sure that all connections are solid, and all devices are powered up before launching QLab, and that you quit QLab before disconnecting any connected devices.

(Similarly, it’s never a good idea to close a laptop lid or otherwise put a computer to sleep while QLab is running, as this effectively disconnects all connected devices.)

If that’s not the problem, and Chris’s other suggestions don’t help, then please do contact us directly at sup...@figure53.com, and we’ll help figure out what’s going on!

-Andy

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

​

[Søren Andreasen]

Similar issue here. Despite having the correct follow action, and group setting (start first child and enter into group) qlab will occasionally just not go into the group.. this render the application useless for professional use. 

[Sam Kusnetz]

Hello Søren

You’ve replied to message from 2015, so I’m not completely sure whether the issue you’re having is related or not.

Can you please tell me what version of QLab and what version of macOS you are using?

The original message referred to a version of QLab and a version of macOS that are both quite out of date, so it’s difficult to say whether the issue they were having was solved by a simple update.

I can say for sure that the issue you’re describing is not one we’ve heard before, from either our amateur or our professional users.

Best

Sam

—

Sam Kusnetz | Figure 53

s...@figure53.com

--
Contact support anytime: sup...@figure53.com
Follow Figure 53 on Twitter: https://twitter.com/Figure53
User Group Code of Conduct: https://figure53.com/help/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/d6133d43-462e-473e-8bec-27b93252a818%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Søren Andreasen]

Hello,

Thank you for getting back so quickly. Having used qlab extensively for several years now, I keep running in to this bug (if you will) despite it not being very often. I have used qlab mostly in permanent installations, and the most recently i experienced this issue again (today)is on osx 10.10.05. qlab version 3.1.23.  Restarting qlab fixes it, but only until it happens again. 

Is there anything else I can provide you of information?

[Sam Kusnetz]

Hi Søren

I definitely recommend updating to QLab 3.2.14, which is the most recent release and which contains all the known bug fixes for QLab.

I’m afraid I don’t have much else to offer since I’ve never heard of this problem before, but I can say comfortably that there’s really no sense troubleshooting without updating.

Best

Sam

—

Sam Kusnetz | Figure 53

s...@figure53.com

To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/a13553af-7702-411f-8556-41b8927738d4%40googlegroups.com.