Help to identify what this console messages tells me....

Blunder82's picture

Hi Guys,

I understand the basics of this message, but i have some trouble understanding why this happens. Can I read anything out this console message:

9/21/10 8:36:21 PM QLab[306] *** Message from : OpenGL error 0x0502 (invalid operation)

9/21/10 8:36:21 PM QLab[306] *** Message from : Execution failed at time 0.000

9/21/10 8:36:21 PM QLab[306] *** Message from : Execution failed at time 0.000

9/21/10 8:36:21 PM QLab[306] *** Message from : Execution failed at time 0.000

9/21/10 8:36:21 PM QLab[306] *** Message from : Execution failed at time 0.000

Best, Rasmus

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

cybero's picture
Re: Help to identify what this console messages tells me....

Blunder82, are you running an nvidia card Mac ?

Have you updated to the latest QLab [2.3.2 build 1154] that had a fix for a still image problem?

It could be that QLab is / was re-presenting the image feed in a fashion that was inaccessible to QLab.

Blunder82's picture
Re: Help to identify what this console messages tells me....

It might have been that, but I was (also hence the late reply) in a hurry to get it to work. I decide to use Quartz crystal to render the movies instead of doing the QC Work realtime. But thanks for the reply i'll test it one of these days.

gtoledo3's picture
Re: Help to identify what this console messages tells me....

Do you get that all the time?

You really ought to consider contacting the makers of QLab. By all means, with a crash with anything QC related, this is definitely a good place to get a quick head's up, but there isn't a lot of info in that one.

Maybe you could let the makers of Qlab know what's happening and what you do to have those console messages trigger. For example, is it something that happens when you play a certain file, or is it something that happens just from messing around with the interface? I'm guessing it's when you load a file that doesn't execute.

That could indicate a problem with the file, a problem with the way Qlab runs the file, or none of the above.