christian/status-indicators
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

NA ProPresenter Mac runs the stage guard too (installed by hand: Stage Screen, port 1025)

Browse Source 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
christian
2026-10-26 16:24:18 -04:00
co-authored by Claude Opus 5.5
parent 9a818f63ca
commit b3e4d77180
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+4 -1
View File
@@ -369,7 +369,10 @@ line again resets the task to plain `Vista.exe`: point it back at the script aft
## ProPresenter guard (every location with ProPresenter on the Companion Mac)
`prop_guard.py` (LaunchAgent `org.waterschurch.prop-guard`, log `~/Library/Logs/prop-guard.log`) is started by
`install.sh` on any Mac with `/Applications/ProPresenter*.app`: today SC and WS, and AB with its next package. When a
`install.sh` on any Mac with `/Applications/ProPresenter*.app`: today SC and WS, and AB with its next package. NA's
ProPresenter is not on the Companion Mac: its guard was copied by hand (na-propresenter-mac, cfg
`{"stage_screen": "Stage Screen", "api": "http://127.0.0.1:1025"}`; to update it, copy `prop_guard.py` there and
`launchctl kickstart -k gui/$(id -u)/org.waterschurch.prop-guard`). When a
song (a presentation with a timeline) comes up and its first slide's macro left the **Stage Display** screen (else the
first stage screen) on a layout without "Worship" in its name, it is set to **Worship** within 12 s; later picks are left
alone, and so is a song that was already up when the guard started. ProPresenter's network port differs per Mac