QLab v3 upgrade to Qlab v4 (Lighting question)

[Paul James]

Hi, 

I have just upgraded from Qlab v3 video to Qlab V4 video

I use LXcontrol program in Qlab v3 via Enttec DMX USB Pro using Qlab Midi MSC which works just fine for the simple lighting plots I use. 

However now I have Qlab 4 I would like to take a look at what Qlab 4 lights have to offer, is there anyway I can do this without buying a licence at this stage?

Would I have to re-wright all lighting cues or can you import somehow?

Thank you in advance.

Paul

[Joshua Langman]

Go to QLab > Start Demo Mode.

[Chris Ashworth]

Good morning Paul,

A few ways to test lighting:

• You can use up to 16 DMX channels of lighting for free; if your show uses 16 or fewer lights then you do not need a paid license.

• You can program more than 16 channels in the free version, but just the first 16 will be sent to the lights.

• Demo mode turns on all features for 20 minutes: QLab —> Start Demo Mode…

• You can rent a Lighting license for $4 / day.

There is not a way to import lighting cues from other programs, so it would require rewriting them in QLab.

Best,

Chris

[Paul James]

Thank you Chris, 

I've had a look but un able to get the usb out putting to the Enttec DMX USB Pro to work with Qlab. Do you have a instruction guide I could follow please. At the moment I have Qlab 3 & 4 setup to output to LXconsole. All shows use way more than 16 channels but having 16 to play with will be just fine to get things working and to give me some idea what I need to do.

I like the idea of putting all my lighting plots into Qlab it would make things so much easier having it all in one place, but I have 6 working shows with very involved lighting plots which would take a lot of time to chance so would need to do them over time. That would mean I would have to work on one show at a time, leaving me with the need to change from Qlab Lighting to LXconsole with the risk of knocking my setting out.  

Regards 

Paul

[Chris Ashworth]

Hi Paul,

QLab uses macOS’s built-in drivers to communicate with USB DMX devices, and sometimes if there are separate drivers also installed, they can conflict and prevent QLab from reaching the USB device. If separate drivers are installed you’ll need to uninstall them in order to fix this.

To do that, open a Finder window on your Mac and navigate to `/Library/Extensions` (which is not the same Library as the one inside your home folder... this is at the top level of your computer’s hard disk.)

In there you may find a file called “D2xxHelper.kext.” Drag that file to the Desktop, and give your computer your password when it asks. Then reboot your Mac. QLab should now be able to work with your USB DMX device. 

Also: keep a copy of that driver rather than deleting it, in case you need it for LXConsole.

If that doesn’t work, please write us at sup...@figure53.com and we can continue troubleshooting by looking at console logs to make sure it’s a driver problem, and using some Terminal commands to try to track down where the driver might be hiding if it's not in the normal place. 

Best,

Chris

[Paul James]

Thanks Chris

Playing safe with the show machines I loaded Qlab4 up as the edit only option (in the Manage Licences) on a old mid 2010 mac (retired from show use) to test lights and bingo after I following your instructions it worked. But I’m not sure why lights stop working when I open the Audition Window, soon as I shut down the Audition Window light worked again. 

In any case for now I can have a play with the light to get a feel.

Thank you very much for your help

Paul

[Chris Ashworth]

Hi Paul,

The audition window is generally intended to allow you to try things without “sending them to the stage”.

Thus, when the audition window is open the light dashboard is acting in a kind of “blind mode” where the actual light values are not sent out. When the audition window is closed the light dashboard will revert back to the state it was in when the window was opened.

Worth noting: In QLab 4.0 through 4.2 the light engine disabled output entirely if the audition window was opened. Starting in 4.3 it changes to freeze the outgoing values rather than disable output entirely.

Best,

Chris