QLab Scripts

[Victoria Elizabeth]

Hey! 

Has anyone been having issues with Apple M4s on Sequoia 15.6 and QLab 5.5.10 with firing scripts?

I'm firing a script from a QCART computer that I need to open show files on my QLab A/B computers. My other scripts to open/close QLab etc all work so I know that the QCart computer can control the others but for some reason I've been getting errors when trying to open show files. I've had success with these exact scripts on 4x other installs (the last one running the exact same MacOàs) but for some reason have errors now. 

I've allowed the Remote Applescript permissions, Local Network permissions and have given QLab and Finder full disk access but no luck. 

I've attached photos of the script and the message I get from QLab on the receiving computers. Any advice would be greatly appreciated! 

Thanks! 

[Sam Kusnetz]

Hi Victoria

Try this phrasing:

tell application "QLab" of machine "eppc://etc..." to open POSIX file 
"/Users/blah/blah/workspace.qlab5”

Does that work?

sk

—

Sam Kusnetz (he/him) | Figure 53

s...@figure53.com

--
Contact support anytime: sup...@figure53.com
User Group Code of Conduct: https://qlab.app/code-of-conduct/
 
Instagram: https://www.instagram.com/Figure53
TikTok: https://www.tiktok.com/@QLab.app
Bluesky: https://bsky.app/profile/qlab.app
---
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.
To view this discussion visit https://groups.google.com/d/msgid/qlab/CAL0%3DYNdgenOA_kGwTHBT6_NNBc%3D3SFSYCK5ZhmV1tjqTjMWcxw%40mail.gmail.com.

[Victoria Elizabeth]

Hey! 

Unfortunately it doesn't, and I've attached the message I got below. 

Thanks! 

Victoria

To view this discussion visit https://groups.google.com/d/msgid/qlab/CAOOK5AZgDYFnsbua4%3DQsMyh1Bs4SO1EdFWopq3-otQRidJj5DA%40mail.gmail.com.

[Sam Kusnetz]

Hi there

 

Please send your workspace file to support! We can help.

 

Best

Sam

––
Sam Kusnetz [he/him/his] (what is this?)
Figure 53
https://qlab.app | https://figure53.com

On Apr 4, 2026 at 7:40 PM -0400, Victoria Elizabeth <vick...@gmail.com>, wrote:

Hey! 

Unfortunately it doesn't, and I've attached the message I got below. 

Thanks! 

Victoria

<1000015806.jpg>

On Sat, Apr 4, 2026, 5:56 p.m. Sam Kusnetz <s...@figure53.com> wrote:

Hi Victoria

Try this phrasing:

tell application "QLab" of machine "eppc://etc..." to open POSIX file  
"/Users/blah/blah/workspace.qlab5”

Does that work?

sk

—

Sam Kusnetz (he/him) | Figure 53

s...@figure53.com

On Apr 4, 2026 at 5:29:27 PM, Victoria Elizabeth <vick...@gmail.com> wrote:

Hey! 

Has anyone been having issues with Apple M4s on Sequoia 15.6 and QLab 5.5.10 with firing scripts?

I'm firing a script from a QCART computer that I need to open show files on my QLab A/B computers. My other scripts to open/close QLab etc all work so I know that the QCart computer can control the others but for some reason I've been getting errors when trying to open show files. I've had success with these exact scripts on 4x other installs (the last one running the exact same MacOàs) but for some reason have errors now. 

I've allowed the Remote Applescript permissions, Local Network permissions and have given QLab and Finder full disk access but no luck. 

I've attached photos of the script and the message I get from QLab on the receiving computers. Any advice would be greatly appreciated! 

Thanks! 
<1000015809.jpg>

To view this discussion visit https://groups.google.com/d/msgid/qlab/CAL0%3DYNeSC-bEbaPH8NxTu-o2bXunN5er-7XxL3w9YLq__Apzag%40mail.gmail.com.

[Victoria Elizabeth]

Hello,

I'm chatting with someone from Figure 53 trying to figure it out. 

He suggested removing gaps from the file path. Once I did that, I got a new message I don't understand. I've attached the photo below. 

Thanks! 

Victoria 

To view this discussion visit https://groups.google.com/d/msgid/qlab/7ccc381d-cab5-4166-b6fa-0b363695495d%40Spark.

[Drew]

removing the gaps from the file path needs to be done on both machines otherwise the computer won't understand where it is targeting.  MacOS doesn't like spaces in file names for this sort of thing but if you wrap the QLAb A FILES part in quotes it knows that part of the file path has spaces.  

eg: /Users/qlaba/Documents/"QLAB A FILES"/SMILE/SMILE.qlab5

Best practice if you want to do that would be to have qlab-a-files as the directory name instead of QLAB A FILES.  

I hope this helps.

[Paul]

I have this script working with a few caveats - there doesn't seem to a way to test if the file exists on the remote computer, so you will never see an error on the local machine. This first opens QLab and then opens the file. No problem with file name with spaces just enclose them in quotes. 

-- open Qlab workspace on remote machine

set remoteHost to "192.168.1.184"

set remoteHost to text returned of (display dialog "Enter hostname/IP address of remote Qlab machine" default answer remoteHost)

set user to "qlab"

set pw to text returned of (display dialog "pw for " & user default answer "")

set RemoteMachine to "eppc://" & user & ":" & pw & "@" & remoteHost

-- define the file path of the workspace on the remote computer

set remoteFilepath to "/Users/user/Documents/shows/some show file.qlab5"

-- trying to check if file exists, but this does not appear to work ??

-- TODO find a way to check if file exists remotely

tell application "Finder" of machine RemoteMachine to set fileOK to (exists file remoteFilepath)

display dialog fileOK as string with title "file exists on remote machine?"

set errors to {}

tell application "Finder" of machine RemoteMachine

-- open QLab [note the activate command doesn't seem to work remotely]

try

-- this always sseems to generate an 'Apple Event' error, so sliently ignore

open application id "com.figure53.QLab.5"

end try

end tell

-- now tell QLab to open the remote file

tell application "QLab" of machine RemoteMachine

-- if this file does not exist, there doesn't seem to be any method of catching the error

open remoteFilepath

end tell

Tested with v 5.5.10 and 13.7.8. The error you got about "unable to open .." generally means the file does not exist (or not readable by the user)

In general it might be better to avoid this by having Qlab Preferences to open last Workspace and (if no projectors involved) have QLab in the login in  items. Then starting the machine everything should come back as you left it. You probably need to do a rig check locally so the remote loading is probably best avoided.