Current cue name to variable

[Rose O]

Hi,

Currently I'm trying to do a setup to send commands to an ETC Ion via UDP for running cues. What I would like to do is use the current cue's name as the input for the command that is sent for ease of programming. I'm struggling to find documentation on this.

Here is what I'm testing so far:

tell application "QLab"

tell front workspace

set com to "Cue 1 1.0"

set address to "localhost"

set portNo to 9000

do shell script "echo '" & com & "' | nc -uw 1 " & address & " " & portNo

end tell

end tell

It does seem to cause a bit of noticeable lag though I can see the command fires instantly on Go. Is there anyway I can background this task so QLab doesn't wait on the shell script finishing?

Thanks,

Rose

[Rose O]

Oh and one last thing, is there any way I can get global variables anyway to be used for the address and port of the desk?

[luckydave]

On Thursday, 14 May 2015 20:04:25 UTC+1, Rose O wrote:

Hi,

Currently I'm trying to do a setup to send commands to an ETC Ion via UDP for running cues. What I would like to do is use the current cue's name as the input for the command that is sent for ease of programming.

You may want to check out QLX. It might already have the solutions you're looking for, but even if not, it uses very clever ways of storing variables in cues so other cues can access them:

http://www.qlx.io/

-- 
luckydave

[Rose O]

Oh awesome thank you, looks like someone else has done the hard work already.

Thanks,

Rose

[Alec Sparks]

:D

[Rose O]

In fact I think a UK touring show came in last year using QLX with a Nomad Puck, Pride and Predujice produced by Richard Darbourne. I thought it was custom stuff they had figured out. Looks like we had the same chain of thoughts anyway Alec, you've saved me a fair bit of time and your source is great for getting to know some of the operations you can do. Thanks for your great work!

Is there any kind of fuller documentation you can link me too? Most things I've seen are just little examples lacking in any substance.

Thanks,
Rose

[Rose O]

Just to clarify the QLab Applescript interface not QLX, that is well documented :)

[Chris Ashworth]

Hi Rose,

The three best places to start with AppleScript are:

1) Viewing the scripting definition file from QLab via Apple’s Script Editor application.  (“File” —> “Open Dictionary” —> Pick QLab 3 from the list)

2) https://figure53.hostedwiki.co/pages/QLab%20Scripts%20and%20Macros

3) http://qlabcookbook.com/  (Not strictly AppleScript but has plenty of useful examples among the samples.)

[Adam B]

Hi Rose,

You can also do this using OSC raw strings.
Syntax is the same as QLX.

To see what's happening I also usually designate a user id in the string so from the diagnostics window in EOS you can see if string is being received.

From memory string would be something like:

$ </5> Cue # * \r

Replace # with cue list number
Replace * with cue number

In the OSC setup you will need to put the IP address of the MAIN console and put the port number you have setup on the EOS/GIO/ION as the serial RX port.

Unfortunately i can't get access to a computer for the moment to test and confirm this bit it's quite simple.

ETC Serial command list
http://www.etcconnect.com/Support/Articles/Eos-Family-Serial-Command-Syntax.aspx


Hope this helps.
Adam