[QLab] Using Qlab to control Keynote on another Mac

[Filip Vandueren]

These script cues worked for me (working on a headless second mac).
Unbelieveable, Been craving this for years.
Just make sure that whenever a script might take some time (like
opening a file or an app),
you don't put it together with sound cues, because applescript hangs
the autocontinue-chain untill it's completed.

-- open remote keynote and check if it's opened

set m to "eppc://user:pa...@machine.local"

tell application "Finder" of machine m
using terms from application "Finder"
open "Macintosh HD:Users:vandueren:Documents:klank Anne
Frank:projecties:anne frank proj."
end using terms from
end tell

tell application "Keynote" of machine m
using terms from application "Keynote"
set sl to the name of slideshow 1
end using terms from
end tell

display dialog sl & " is opened"

-- goto slide 1 and start

set m to "eppc://user:pa...@machine.local"

tell application "Keynote" of machine m
using terms from application "Keynote"
tell slideshow 1 to show slide 1
start slideshow 1
end using terms from
end tell

-- show a particular slide

set m to "eppc://user:pa...@machine.local"

tell application "Keynote" of machine m
using terms from application "Keynote"
tell slideshow 1 to show slide 3
end using terms from
end tell

-- advance (keynote should be in playing mode)

set m to "eppc://user:pa...@machine.local"

tell application "Keynote" of machine m
using terms from application "Keynote"
advance
end using terms from
end tell

Some bugs I've noticed:

Selecting a previous script cue while another script is armed, editing
the source, then clicking somewhere will actually replace the source
of the armed
clip, not the one in who's inspector you were changing the code ?

Haven't found a way to 'compile' the code, other than clicking on the
cue icon again, so that's where I picked up that habit.
________________________________________________________
WHEN REPLYING, PLEASE QUOTE ONLY WHAT YOU NEED. Thanks!
Change your preferences or unsubscribe here:
http://lists.figure53.com/listinfo.cgi/qlab-figure53.com

[Christopher Ashworth]

Thanks for these script examples Filip! Very cool.

On Sep 2, 2009, at 9:50 PM, Filip Vandueren wrote:

> These script cues worked for me (working on a headless second mac).
> Unbelieveable, Been craving this for years.
> Just make sure that whenever a script might take some time (like
> opening a file or an app),
> you don't put it together with sound cues, because applescript hangs
> the autocontinue-chain untill it's completed.

Yeah, unfortunately AppleScript can only run in the main thread, so
QLab must run them there. Therefore for long-running scripts
everything stalls until the script is complete.

> Some bugs I've noticed:
>
> Selecting a previous script cue while another script is armed,
> editing the source, then clicking somewhere will actually replace
> the source of the armed clip, not the one in who's inspector you
> were changing the code ?

Interesting, I'll check this out.

> Haven't found a way to 'compile' the code, other than clicking on
> the cue icon again, so that's where I picked up that habit.

Good idea, I'll add a "compile" button to the inspector.

Best,
Chris

[Paul Gotch]

On Thu, Sep 03, 2009 at 06:35:53AM -0400, Christopher Ashworth wrote:
> Good idea, I'll add a "compile" button to the inspector.

Hum should it automatically be compiled when the cue is loaded? Like
audio is pre-cached when an audio cue is made ready to run?

-p
--
Paul Gotch
--------------------------------------------------------------------

[Christopher Ashworth]

On Sep 3, 2009, at 6:43 AM, Paul Gotch wrote:

> On Thu, Sep 03, 2009 at 06:35:53AM -0400, Christopher Ashworth wrote:
>> Good idea, I'll add a "compile" button to the inspector.
>
> Hum should it automatically be compiled when the cue is loaded? Like
> audio is pre-cached when an audio cue is made ready to run?

It is, yes, and it is also compiled any time the source code is
actually set on the cue. It's just that right now there's not an
obvious way to cause that string to be set, thus triggering a
compilation. There's some space available for a compile button, which
would actually be a "commit my changes" button, which would trigger
the compilation. At least at first blush, it seems a good addition.

-C