Telnet / Scripting /

[Wayde Buttimore]

I have been using qlab for years and love it. I am now using the
applescripts to do telnet commands into watchout, video switchers,
scalers, relays for rigging and screen motors and so on..
Im now at the point where the applescripts are no longer working for
me as i need to fire telnet commands to say 5 telnet servers at once.
and with qlab running applescripts in the main thread this really cant
be done. Now im not a programer, I just figure stuff out to work for
me at the time. I dont like how qlab "pauses" when you run an
applescript..
is there anyway around this? How can i fire a cue that will make a
script run outside of qlab?
can i write a python script with threading and send the arguments as
a variable from qlab to the python script to fire these commands to
many telnet devices.

i hope this makes sense of what im tryin to do.

Thanks Heaps,

Wayde

[Andy Leviss]

On Sun, Jan 22, 2012 at 12:25 PM, Wayde Buttimore
<wayde.b...@gmail.com> wrote:
>  I dont like how qlab "pauses" when you run an
> applescript..
> is there anyway around this? How can i fire a cue that will make a
> script run outside of qlab?

I don't know if it will have the performance boost you need, but you
could run MIDIpipe, which can trigger AppleScripts based on MIDI
messages. So QLab sends a MIDI message to the IAC bus, and then
MIDIpipe triggers the script based on that. Worth a shot, since it's
free and easy to set up.

--A

------------------------------------------------------------------------------------------------
Andy Leviss
ETCP Certified Entertainment Electrician #1251

DucksEchoSound.com
Home of the Perfect Pickle Mini Chain Hoist Controller
and the MR-6 MIDI Remote, 2011 Live Design Product of the Year

[Wayde Buttimore]

Looks like a great work around.
Trying it now.. but my mac book pro (not my live production mac)
doesnt seem to be sending the midi from qlab to midiport..
hmm.. looking into it now..
Thanks heaps!!!

On Jan 25, 8:57 am, Andy Leviss <a...@ducksecho.com> wrote:
> On Sun, Jan 22, 2012 at 12:25 PM, Wayde Buttimore
>

[Andy Leviss]

On Wed, Jan 25, 2012 at 11:37 AM, Wayde Buttimore
<wayde.b...@gmail.com> wrote:
> Trying it now.. but my mac book pro (not my live production mac)
> doesnt seem to be sending the midi from qlab to midiport..
> hmm.. looking into it now..

You may have to set up an IAC bus in Audio/MIDI Setup, and then patch
to that output/input in each program.

--A

------------------------------------------------------------------------------------------------

[Christopher Ashworth]

On Jan 22, 2012, at 12:25 PM, Wayde Buttimore wrote:

> I dont like how qlab "pauses" when you run an
> applescript..

Just to clarify the technical reason behind this:

AppleScript is designed to run only on the main thread, so QLab is required to run it on the main thread.

Therefore Script Cues will delay any further processing on the main thread (e.g. drawing the GUI) until the script is done.

[Rich Walsh]

So, in theory, you could save your scripts as applications and run several of them at once in their own independent threads, possibly "ignoring application responses" in QLab... I suspect MidiPipe will have the same problem as QLab. In QLab Button Bar I have 20 independent instances of the OSA Script Controller, which appears to allow 20 scripts to run in parallel threads (although I don't really know enough about programming to be sure this is happening).

Combining multiple Script Cues into one script will help, if that's possible. There's always MIDI Show Control...

Rich

[ra byn (robin)]

On Wed, January 25, 2012 11:19 am, Rich Walsh wrote:
> Combining multiple Script Cues into one script will help, if that's
> possible. There's always MIDI Show Control...

Or a native telnet cue for Qlab?

[Charles Coes]

Nope, you can get there via scripting though.

> --
> Change your preferences or unsubscribe here:
> http://groups.google.com/group/qlab
>
> Follow Figure 53 on Twitter: http://twitter.com/Figure53

[Wayde Buttimore]

A telnet cue would make Qlab a even more powerful show control
system..
Could do it like the midi and audio patch.. have all your telnet
address and ports (and user names/password if needed)
then on the cue have a select telnet out put and a txt box (like apple
script) where each line is a command to send

I would be happy to beta test this

:) Hope it gets added :)

[Andy Dolph]

I know John Huntington at City Tech is really big on working this way and has found it to be very powerful - I'd like to control Qlab via telnet too.

Sent from my iPhone

[ra byn (robin)]

Adding Telnet would give native access to Light Factory which would allow
for me to move a theater using SFX 5.6 to Qlab.

Otherwise they would need to use midi cues which are somewhat limited &
way more than the house tech is going to handle any time soon.

In LF, any incoming telnet cue is the same as any command line entry.

BO = black out
1-512 @ 100 = channels 1 thru 512 @ full
etc...

I'll gladly beta test a telnet out cue if one is added!

*