Move up and down a specific cue list

[SSound]

Hope this isn't too stupid but I'm in need of a hot key that moves up and another that moves down a specific cue list.  Hopefully I'm not missing anything too obvious - is this a script job?

Thanks

Tom

[micpool]

Dont the arrow keys do what you want?

[SSound]

It's so that MIDI remote can move a cue list in the background up and down whilst the screen remains on the Main Cue List.

Am I along the right lines with something like...

tell (cue list whose q name is “Main Cue List“)

moveSelectionUp

end tell

[Chris Ashworth]

Do you want to move the selection, or move the playhead?

[micpool]

Assuming you want to move the playhead of a hidden cue list, blind (Very brave)

Does this work for you 

tell application id "com.figure53.qlab.3" to tell (the first cue list in workspace 1 whose q name is "List2") --your hidden cue list name goes here

set thecurrentcue to the playback position

set thecurrentcue to cue after thecurrentcue

set the playback position to thecurrentcue

end tell

Mic

[SSound]

That's exactly thanks Mic!  It's more for scrolling through tracks for testing purposes than for live show conditions.

[micpool]

Good!

Variations of that script allow you to have separate controls for Play Panic Next and Previous in each cue list in workspaces with multiple cue lists with independent playheads, entirely independent of the current selection.

To make it  even more useful, include hotkeys to switch the current cuelist

tell application id "com.figure53.qlab.3" to tell front workspace

set current cue list to first cue list whose q name is "List1"

end tell

etc

Mic

[Rich Walsh]

You can use MSC SEQUENCE_+ & SEQUENCE_- to target a specific cuelist (just give it a number). Make two MSC cues on hot keys and use the IAC Bus to loopback into QLab.

You can also GO a specific cuelist like this by giving it a number and sending an MSC GO to GO that cue number. This works for STOP too (pauses the cuelist), but sadly not RESUME (unless you remove the cue number and just resume all paused cues).

You'd think you could do something with /cue/{number}/playbackPositionNumber/+1, but it doesn't seem to work – probably because cue number is a string. Mind you, I can't currently get OSC to start a cuelist either…

(Quick tests: may have missed something.)

Rich

--
--
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+uns...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[micpool]

On Saturday, August 22, 2015 at 1:49:29 AM UTC+1, Rich Walsh wrote:

You can also GO a specific cuelist like this by giving it a number and sending an MSC GO to GO that cue number. This works for STOP too (pauses the cuelist), but sadly not RESUME (unless you remove the cue number and just resume all paused cues).

I tried that first and couldn't get it to work. Isn't the cue list title  a name rather than a number?

Mic

[Rich Walsh]

Fixed part of OSC problem: messages between workspaces not working (how do you do that?); you can GO a cuelist with /cue/{number}/start after all.

Rich

[Rich Walsh]

I think it works if you put an MSC-acceptable string in the cue number field (not the cue name), eg: "1.2.3.4.5" is OK (but "Charlie" wouldn't be).

Rich

[Charlie Richmond]

On 21 August 2015 at 18:06, Rich Walsh <rich...@mac.com> wrote:

I think it works if you put an MSC-acceptable string in the cue number field (not the cue name), eg: "1.2.3.4.5" is OK (but "Charlie" wouldn't be).

​What???

[micpool]

I'm really confused

I can't get it to do what your doing using OSC or MSC

The cue list name can't be a cue number because I can give a cue the same number. 

Mic

[micpool]

Ah, I'm not confused anymore!!

I never knew you could give a cue list a Q number.

Mic

[micpool]

On Saturday, August 22, 2015 at 2:01:05 AM UTC+1, Rich Walsh wrote:

messages between workspaces not working (how do you do that?);

/workspace/OSC.cues/cue/4/start

Workspaces may be addressed either by their display name or their unique ID. For all OSC methods shown below of the form /workspace/{id}/... the {id} may be either the display name or unique ID.

Note, however, that addressing by display name will work only if the display name is composed of characters allowed in OSC method names. This does NOT include spaces, unicode, diacritical, or other "special" characters.

Mic