Q-Lab doesn't recognize a different projector from set-up unit

[Jonathan G]

Hi All,

Has anybody run into this problem and discovered a work-around?

I developed and refined a cue list using a projector different from the one in the theater but on the same Mac to be used in the show.  Every thing was working great--just video cues with the sound cues to be added today.

Yesterday was the load, and when I connected the theaters projector to the system, Q-Lab does not recognize the new projector--it doesn't show up as a screen in the list even though it's working just fine at the OS level ( If I mirror the screens as a test I see what's on the monitor).  I've tried checking the Separate Space setting in Mission Control on and off, and restarting.

• Should I create a fresh space in Q-lab, set up the surface, and then copy and past the cues from the other space?
  
• Should I create a package, and then reload it, and then map the surfaces to the new projector screen?
  
• Do I need to start all over again and enter the cues manually?

This is a show stopper and I'm hoping someone can help me.

Thanks,

Jonathan

[luckydave]

On August 15, 2015 at 7:49:02 AM, Jonathan G (jon...@gmail.com) wrote:

Yesterday was the load, and when I connected the theaters projector to the system, Q-Lab does not recognize the new projector--it doesn't show up as a screen in the list even though it's working just fine at the OS level ( If I mirror the screens as a test I see what's on the monitor).  I've tried checking the Separate Space setting in Mission Control on and off, and restarting.

First, ensure your projector is connected before you start QLab. When QLab launches, it initializes communication with the devices it will use for the show, so if those settings change, such as connecting a projector, you'll need to quit and relaunch QLab, to be sure it has proper communication established with the new device.

Next, in QLab, open Video Settings (click the gear icon at the bottom right of the workspace window, and select Video from the list on the left). Click the Edit button on the surface you're using in your cues (likely called "Surface 2", if it was automatically created). From the list of screens on the left, select the projector you used previously, and use the Replace Screen button to select the new projector.

Note that if you created your work on a 1024x768 projector, and there's a 1080p projector in the venue, you'll need to change the surface's pixel dimensions, which you can do at the top right of the surface editor window. In such a case, you'll need to switch 1024x768 to 1920x1080. One more headache in a situation like that: if you used any custom geometry, you'll probably need to place your cues again, because they're relative to a smaller 4:3 screen, and now you're on a larger 16:9 screen.

-- 
luckydave

[Jonathan G]

Thanks, Dave.  I thought I did all that, but I'll make sure.  I used to be a real-time systems programmer, so I understand that the App is reading the device table at start-up.  But I still thought I was seeing anomalous behavior even though I quit QLab and restarted the OS with the new device configuration. Even though I see the new projector in the list of screens, when I re-patch the surface, it still displays on the monitor and not on the projector.  Otherwise, I wouldn't have posted the problem.

Thanks Again, Jonathan 

[Jonathan G]

OK. Here's what I found that makes it work:

Follow your steps, but after opening QLab, I created a fresh unnamed workspace, and then added a video cue. 

I then went to  the video setting and mapped a surface to the new screen which shows up as Wide projection. I then checked that the cue works correctly, which it did. Then I opened the Workspace created in my studio which had a different hardware configuration, and assigned  the surface to the screen Wide projection.  It then worked correctly. 

without taking the extra step of creating a blank workspace before I opened the old one, it did not work.  QLab was confused about where to send the images even though I had patched it to the new device.

Thanks again for your help.