Goto cue across cuelists

476 views
Skip to first unread message

Tom Quinn

unread,
Nov 8, 2016, 8:08:31 PM11/8/16
to ql...@googlegroups.com
Hello!
I'm trying to move between cue lists with the goto cue... Is that supposed to work? 

I have two lists, at the bottom of the first, I've got a goto cue targeting the first cue of the second cue list, all in the same workspace... It doesn't go when fired, the selector bar goes away and there's no cue on standby.

Qlab version 3.1.24
Osx 10.9.5

Thanks!

------------------------------------
Tom Quinn
T...@battle4heaven.com
877-793-5175
www.battle4heaven.com

vanmeel...@planet.nl

unread,
Nov 9, 2016, 3:50:03 AM11/9/16
to QLab
Ha Tom try a startcue, maybe thats what your looking for.

cheers Roland 

micpool

unread,
Nov 9, 2016, 6:02:43 AM11/9/16
to QLab
If you go to a cue in a hidden list the playback position of the hidden list will be the cue you went to.

The Go button targets the current frontmost list so if you want to trigger the cue in the hidden list you will need to create a hotkey to trigger that list

Alternatively if you want to goto a cue and switch to the list it is in you will need a bit of script.

put this script in a script cue  in a fire all group with your goto cue

tell application id "com.figure53.qlab.3" to tell front workspace
set current cue list to first cue list whose q name is "Reh List"--Change to name of your cue list
end tell

Mic

Tom Quinn

unread,
Nov 9, 2016, 10:16:08 AM11/9/16
to ql...@googlegroups.com
Curious. That's exactly what I am looking to do Micpool, Thanks!

Perhaps a feature request, to enhance the goto cue so the playback head moves within the workspace, not just the current cue list.

Thanks!

------------------------------------
Tom Quinn
T...@battle4heaven.com
877-793-5175
www.battle4heaven.com

--
--
Change your preferences or unsubscribe here:
http://groups.google.com/group/qlab
 
Follow Figure 53 on Twitter: http://twitter.com/Figure53
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/03e331b4-c313-4de8-91b7-871da18eb3fb%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

micpool

unread,
Nov 10, 2016, 12:35:11 PM11/10/16
to QLab
On Wednesday, November 9, 2016 at 3:16:08 PM UTC, sprsndman wrote:

Perhaps a feature request, to enhance the goto cue so the playback head moves within the workspace, not just the current cue list.


Except a workspace can have multiple playback heads (1 in each cuelist) although only 1 is controlled by the standard GO button/Key/remote at any one time (the playback head in the visible cue list)


Mic
 


To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.

Tom Quinn

unread,
Nov 10, 2016, 3:28:56 PM11/10/16
to ql...@googlegroups.com
that is true, however, a goto cue can only target one cue, and you must have unique cue #'s across an entire workspace, tying those together it would seem like a reasonable ask... no?

course the more I think about it, perhaps a new cue type, 'global goto' cue might be better? though I'm not sure where one would use a goto cue on a secondary cue list when you can't see what's happening there, the possibility would exist I suppose, I just can't currently come up with a situation where that would be useful.

------------------------------------
Tom Quinn
T...@battle4heaven.com
877-793-5175
www.battle4heaven.com

To unsubscribe from this group and stop receiving emails from it, send an email to qlab+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/43177258-132c-4453-82fe-68151c168641%40googlegroups.com.

micpool

unread,
Nov 10, 2016, 8:05:51 PM11/10/16
to QLab
The most common use of goto in a blind cue list would be when you have a cue list of click tracks operated by a MIDI controller controlled by the MD.

A go to in the main list referring to a cue in a hidden list would cue up the hidden list to await the MDs go button while allowing cues to continue to be run from the main list by the sound op.

Another example would be ta list for foley footsteps on a hotkey (MIDI or keyboard), So the main cue list starts the music and the operator then uses the hotkey to step through a long list of footsteps on sand cues, when the character reaches the bit of the stage painted blue to represent the sea, the main list cues up the hidden list to a later set of cues in that list e.g  starting at Q500 which are footsteps in water. Mean while in a 3rd list the MD has started a click track and the sound operator has done various spot effects in the main list. 

Remember that although you cannot see the hidden lists you can see the cues that are running with in them in the Active cues window.


Mic






Reply all
Reply to author
Forward
Message has been deleted
0 new messages