Q-Lab meets the Microvision

I confirmed with a few quick tests today that the ETC Microvision we'll be using to run the lighting console is able to be triggered via MIDI. This means that the sound software, Q-Lab, can run both lights and sound. There are few things that will be required to make this work. Most important is that Lucrecia will not be able to use "point" cues. Below are some suggestions as to workflow.

1. Cue numbers in the lighting console should follow the following format:

a. Dark Land (play #1) - use any number between 150 - 250
b. Table Land (play #2) - use any number between 260 - 360
c. Number Land (play #3) - use any number between 370 - 470

These will appear as "Control Change" messages in Q-Lab. The Microvision has a preassigned structure as to how Control Change messages correspond to the Cue Numbers. The above designations are based on that format.

2. Lucrecia cue the show in sequence, but skip every 3 to 5 numbers to allow for cues to be inserted. This would only be for organizational sense. Q-Lab can trigger any cue from anywhere in the list in any order we want, but if for some reason Bertie needs to hit "go" on the lighting console, the show should be in as much sequence as possible.

3. I will provide Lucrecia with a cue "checklist." Once she's done cuing, it can be sent to me and I can come in on the second day of tech with a trigger list set up in Q-Lab.

4. The day that I'm at tech (day 2) we'll incorporate lights and sound via a trigger list that will fire both the sound and light cue lists.

I realize this is new territory for some folks, but I am very confident in this working out. I've done this a lot with a mixture of sound equipment, so it's a vetted process. Once we have the basic structure of the cues, it will take very little time to create the list that will manage both. The user interface on Q-Lab is also really easy to understand, so changes can be accommodated pretty quickly too.

Please let me know of any thoughts or concerns.

Yoshi