QLab on Sonoma

197 views
Skip to first unread message

Andy Dolph

unread,
Aug 21, 2025, 5:30:36 PMAug 21
to QLab
How are folks feeling about running QLab on Sonoma?

Our IT folks are pushing for us to update our QLab machines (machines that are used for one off events, not ongoing productions) to Sonoma.  I'm curious about if folks are running into any issues with that at this point?

I remember there being some kind of issue with Sonoma machines and OSC networking?  That could be a showstopper for us if there's not a reliable fix.

Other than that we're mostly doing pretty straight forward audio and video playback with the occasional more complex event with video mapping, multiple outputs, etc...

Thanks!

Andy

Richard Williamson

unread,
Aug 21, 2025, 5:38:54 PMAug 21
to ql...@googlegroups.com, QLab
It’s fine for us on some large scale video and audio installs. We do still have to use some scripts to fix the local network permissions bug (which is not just limited to qlab) but with the scripts in place this hasn’t been an issue 
Sent from my iPhone

On 22 Aug 2025, at 00:30, Andy Dolph <acd...@gmail.com> wrote:


--
Contact support anytime: sup...@figure53.com
User Group Code of Conduct: https://qlab.app/code-of-conduct/
 
Instagram: https://www.instagram.com/Figure53
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/CALBN1sZdBUNYaSb7Zn_7JN4rO1SowJWzBys57D85WDNgx%2BGygw%40mail.gmail.com.

Andy Dolph

unread,
Aug 22, 2025, 10:42:12 AMAug 22
to ql...@googlegroups.com
Would you share the script?

Paul

unread,
Aug 22, 2025, 10:51:05 AMAug 22
to QLab
The issues around networking you allude to are related to "local network permissions" which Apple introduced in MacOS 15 Sequoia so do not affect MacOS 14  Sonoma.  It's pretty hard to keep up I know with such similar names.
This is an Apple / MacOS issue, affecting anything using networking including QLab on MacOS 15; it's seems that the MacOS "loses" or "forgets" permissions for local network even once granted. 
You can find a discussion about it here Hopefully Apple will get round to fixing it someday but knowing Apple I wouldn't hold your breath.

Richard Williamson

unread,
Aug 22, 2025, 10:59:49 AMAug 22
to QLab
Ah yes - apologies, but if useful the script I use to fix is below..

tell application "System Settings"

activate
delay 25

set the current pane to pane id "com.apple.settings.PrivacySecurity.extension"
delay 0.5

tell application "System Events" to tell application process "System Settings"
tell group 4 of scroll area 1 of group 1 of group 2 of splitter group 1 of group 1 of window "Privacy & Security"
click button 9
end tell
delay 0.5

-- Toggle the checkbox for each item in Local Network

set EventArray to {"QLab"}

try
repeat with a from 1 to length of EventArray
set theCurrentListItem to item a of EventArray
tell UI element 1 of row a of outline 1 of scroll area 1 of group 1 of scroll area 1 of group 1 of group 2 of splitter group 1 of group 1 of window 1
click checkbox theCurrentListItem
delay 1
click checkbox theCurrentListItem
delay 1
end tell
-- display dialog theCurrentListItem & " is item " & a & " in the list."
end repeat
on error errstr number errorNumber
display alert "An error has occured." message "Cannot toggle item no." & a & " in Local Network. Please make sure items in EventArray are in the same order as in the Local Network window." as critical buttons {"Terminate script"} default button "Terminate script"
end try

end tell

quit

end tell

--

Andy Dolph

unread,
Aug 22, 2025, 11:14:11 AMAug 22
to ql...@googlegroups.com, QLab
Thank you all!

On Aug 22, 2025, at 10:59 AM, Richard Williamson <ric...@theatre.support> wrote:



Andy Dolph

unread,
Aug 22, 2025, 11:15:24 AMAug 22
to ql...@googlegroups.com, QLab
Richard, do you run that script on boot as an application in login items? Or do you run it from Qlab?

On Aug 22, 2025, at 10:59 AM, Richard Williamson <ric...@theatre.support> wrote:



Chris Devlin

unread,
Aug 27, 2025, 5:49:10 AMAug 27
to QLab
I too would love to know where you're implementing this script, we have the same issue with NDI 

Spranceana Alexandru

unread,
Nov 21, 2025, 12:30:56 PM (3 days ago) Nov 21
to QLab
Can somebody help me  with a script for tahoe, please !🥺

Andy Dolph

unread,
Nov 21, 2025, 1:10:12 PM (2 days ago) Nov 21
to ql...@googlegroups.com, QLab
The feedback I got was that this was no longer necessary at least on Sequoia.  That seems to be proven out by our experience. No idea about Tahoe.

On Nov 21, 2025, at 12:31 PM, Spranceana Alexandru <spranceana...@gmail.com> wrote:

Can somebody help me  with a script for tahoe, please !🥺

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.

Paul

unread,
Nov 22, 2025, 9:37:59 AM (2 days ago) Nov 22
to QLab
There is a ton of confusion around this issue..
Local network permissions were only introduced into MacOS with Sequoia (they had been in iOS for a while) to enhance privacy and security. They permissions for local network never existed in Sonoma so the problem could never have affected that version.

When an application running under Sequoia wanted to access the network (like Qlab sending OSC message) a user dialog box would pop up asking for permission. Once this was allowed things would work fine.
The problem was that MacOS would "forget" the permissoion: after a reboot, the user interface (System Settings) show the permission had been granted but the OS behaved as if they hadn't. The solution was to reset the permissions using tccutil

tccutil reset All bundle.id

so for example (sorry I'm not sure of the exact permission name as running on earlier os version)

tccutil reset LocalNetwork com.figure53.QLab.5


Once you had reset the permission, you could restart the app and the dialog asking for permission would pop up again.

The script above is going through the user interface to do the same thing; if apple changes the user interface the script would break.


This problem was fixed in later versions of Sequoia, so I don't think it should be a problem with Tahoe (unless anyone has observed otherwise?)

Reply all
Reply to author
Forward
0 new messages