[QLab] A script to change cuelists

[Drew Dalzell]

I'm diving into some scripting for Qlab and was wondering if the list has some insight into how to approach this. Compared to the amazing scripting I've been seeing I think should be quite simple.

Here is what I want to do. I have a workspace with about 10 cuelists in it. Each one of these represents a different show that is used throughout daily operation. When this system is operating in show mode the only real interface is a set of 8 control buttons sending MIDI via a MIDI Solutions F8. I'd like to have two buttons that allow the user to move forward and back through the cuelists so that they can select which show they are operating.

Any thoughts?

Drew Dalzell
________________________________________________________
WHEN REPLYING, PLEASE QUOTE ONLY WHAT YOU NEED. Thanks!
Change your preferences or unsubscribe here:
http://lists.figure53.com/listinfo.cgi/qlab-figure53.com

[*]

Meaning that each cue list auto plays when it's selected.
Meaning that you need to be able to stop the existing cue list that is
playing & start at the top of the next cue list?
Meaning that if someone walks away, the rest of the existing cue list
keeps on playing because there is not reset or stop buttons?
Meaning that there is no home position but instead 10 cue lists are in
essense, ramdomly selected. If the first person of the day starts with the
first cue list? Meaning that at some point Qlab reverts back to cue list 1
cue 1?

Or are the two buttons for FF / RR & the other buttons are for PLAY & such...

Or are the cues list auto play? Meaning that as soon as the person selects
them, they start?

If not, does the person see the Qlab screen? If so, how do you represent
10 cues lists on the same screen?

If each cue lists is an auto cuelist, is there a way to have 10 cues lists
controlled by another cuelist with only 10 GOTO commands & some logic
scripts that reset things when a certain button is pushed?

*

On Tue, March 2, 2010 10:23 am, Drew Dalzell wrote:
I'd like to have two buttons that allow the user to move forward and
> back through the cuelists so that they can select which show they are
> operating.

[Stephen Swift]

On Tue, Mar 2, 2010 at 11:23 AM, Drew Dalzell
<drew.d...@drewdalzell.com> wrote:
I'd like to have two buttons that allow the user to move forward and
back through the cuelists so that they can select which show they are
operating.

Here's a script with both versions (select next cue list and select
previous cue list). Make two new script cues. One version includes
the code for the next list, the other... the code for the previous
list. Assign the script MIDI triggers. I tested this with keyboard
triggers. ~Stephen

tell application "QLab"
tell front workspace
set cueLists to every cue list
set currentList to current cue list
end tell
end tell
set listPosition to getPosition(currentList, cueLists)
set totalLists to count cueLists

--Select Next Cue List
if (listPosition < totalLists) then
gotoList(cueLists, listPosition, 1)
end if
--End Select Next Cue List

--Select Prev Cue List
if (listPosition is not equal to 1) then
gotoList(cueLists, listPosition, -1)
end if
--End Select Prev Cue List

on gotoList(l, p, i)
tell application "QLab"
tell front workspace
set newList to item (p + i) of l
set current cue list to newList
end tell
end tell
end gotoList

on getPosition(i, l)
repeat with n from 1 to (count l)
if l's item n is i then return n
end repeat
end getPosition

[Rich Walsh]

On 2 Mar 2010, at 16:23, Drew Dalzell wrote:

> I'd like to have two buttons that allow the user to move forward and
> back through the cuelists so that they can select which show they
> are operating.

This goes forwards and wraps round:

tell front workspace
set allLists to every cue list

set currentList to current cue list

set countLists to count allLists
set searchIndex to 1
repeat until currentList is item searchIndex of allLists
set searchIndex to searchIndex + 1
end repeat
set nextIndex to (searchIndex mod countLists) + 1
set current cue list to item nextIndex of allLists
end tell

This goes backwards and wraps round:

tell front workspace
set allLists to every cue list

set currentList to current cue list

set countLists to count allLists
set searchIndex to countLists
repeat until currentList is item searchIndex of allLists
set searchIndex to searchIndex - 1
end repeat
set previousIndex to ((searchIndex + countLists - 2) mod countLists)
+ 1
set current cue list to item previousIndex of allLists
end tell

Rich

[Drew Dalzell]

Meaning that I have 10 difference shows in the cuelist section to the right of the workspace. Hitting the forward button advances that list to the next show and makes it the focus in the workspace window.

Yes, the other six buttons are GO, STOP, Advance a Cue, Backtrack a Cue, Pause, and Play.

There is a display, but this is for a show that runs adjacent to a large swimming pool so it's a daylight readable LCD and the 8 buttons, no keyboard and mouse. The performers in the show run their own cues. They've been using CD player with a Crestron system controlling it by RS-232 up to this point.

As for home position and other items, that would be dependent upon the content of each current show now, wouldn't it? Some of them are trivia shows where they truly can be randomized, others are linear shows. All of the actually show programming is pretty much done, this is just a way to select different cuelists without needing a mouse or keyboard to do it.

It looks like Rich and Stephen have given some great solutions that I will be trying in the morning.

Drew

[*]

Thanks for sharing Drew. That's not what I was picturing at all.
"Performer triggered cues".

Seems like a solution for those who might have different show based on a
cast change each night. I've had shows were it appeared that I would need
to have different versions of music for each soloist performing the same
piece but so far we've been able to make a version that works for them
all.

*

[Drew Dalzell]

I do a lot of theme park work, so these are shows that will run for years and at peak times of year they can run more than a dozen times a day, with up to 4 different groups of performers each day.

This is a very simple setup, but many of these types of shows are also dealing with full automation for lighting, sound, video all down to one operator, and that is an operator who is pretty much just trained when to hit the big green button.

Drew

On Mar 2, 2010, at 6:21 PM, * wrote:

> Thanks for sharing Drew. That's not what I was picturing at all.
> "Performer triggered cues".
>
> Seems like a solution for those who might have different show based on a
> cast change each night. I've had shows were it appeared that I would need
> to have different versions of music for each soloist performing the same
> piece but so far we've been able to make a version that works for them
> all.
>
> *

________________________________________________________

[Drew Dalzell]

Rich,

Just wanted to let you know that I loaded these scripts and they are doing exactly what I need.  Thank you!

Drew