Lightboard Studio - Bitfocus Companion Auto-Launch & Camera Macro Trigger — Re-Deployment Guide

🔧 Purpose

This configuration ensures that, whenever a kiosk PC boots or any user logs in:

  • Bitfocus Companion launches silently in the background.

  • A PowerShell automation script triggers a predefined Companion button (Page 1 → Button 1) that applies camera color/preset settings via the connected Blackmagic ATEM switcher.

Used in the CIS Lightboard Studio environment where the Blackmagic Micro Camera G2 and ATEM TV Studio HD settings must auto-apply on every login.

🧩 1. System Requirements

  • Windows 10 or 11

  • Bitfocus Companion v4.1.3 (installed to C:\Program Files\Companion\Companion.exe)

  • PowerShell 5.1 (built-in)

  • Local admin rights for the initial setup

  • Folder: C:\Tools (must exist and be readable by all users)

⚙️ 2. Files to Restore / Deploy

File (attached to article) Function Destination
Fire_KickCameraControl.ps1 Waits for Companion HTTP API, then clicks Page 1 → Button 1 twice. C:\Tools\
Fire_KickCameraControl.vbs Launches the PowerShell script silently (hidden). C:\Tools\
Start_Companion_Hidden.vbs Starts Companion silently at logon. C:\Tools\
KickCameraControl.log Created automatically by the script for diagnostics. C:\Tools\

CompanionLightboard_Config.companionconfig

 Saved Companion configuration (ATEM connection + button logic). Anywhere accessible (e.g., C:\Tools\)

All scripts should be UTF-8 encoded with Windows line endings.

📁 3. Folder & Permissions

Run once as admin:

 mkdir C:\Tools icacls "C:\Tools" /grant *S-1-5-32-545:(OI)(CI)(RX) /t

 

This grants read/execute access to all standard users.

🧭 4. Companion Installation & Configuration Import

  1. Install Bitfocus Companion v4.1.3 (standard Windows installer).

  2. Launch Companion once as administrator.

  3. In the web interface (usually http://127.0.0.1:8000 or http://<PC IP>:8000):

    • Go to Settings → Configuration → Import.

    • Choose the provided file (attached to this article):

      CompanionLightboard_Config.companionconfig

    • Confirm overwrite when prompted.

  4. Verify:

    • ATEM module shows Connected (ATEM's IP should be set to 192.168.10.100).

      • In PC's network settings, set Ethernet2 IP manual address to the following (This connects to the ATEM TV Studio HD)

        • IP Address: 192.168.10.10

        • Mask: 255.255.255.0

        • Gateway: blank

    • The button on Page 1 Bank 1 contains your “KickCameraControl” actions.

    • HTTP API is enabled:

      • Settings → Protocols → HTTP API

        • ✅ Enabled

        • Port = 8000

        • Bind = 0.0.0.0 or 192.168.10.10

  5. In Settings → General → Startup, ensure “Start with Windows” = Off.
    (Companion will be launched by script instead.)

🚀 5. Startup Configuration (All Users)

Create two shortcuts in

C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup

 

(a) Hidden Companion Launch

Shortcut name: Start Companion Hidden.lnk
Target:

wscript.exe "C:\Tools\Start_Companion_Hidden.vbs"

 

(b) Auto-Macro Trigger

Shortcut name: Fire KickCameraControl.lnk
Target:

wscript.exe "C:\Tools\Fire_KickCameraControl.vbs"

 

Both shortcuts ensure Companion and the trigger script run for every user at login.

🧪 6. Verification Steps

  1. Log in as a standard user.

  2. Wait ~30 seconds after desktop load.

  3. Check C:\Tools\KickCameraControl.log — a successful run looks like:

    Start Probe http://192.168.10.10:8000 -> True Companion base = http://192.168.10.10:8000 CLICK ... -> HTTP 200 Done (ok1=True, ok2=True)

  4. Confirm cameras/ATEM show the expected color settings.

If you see “CLICK FAILED”, Companion likely wasn’t ready; the script retries automatically.

🔁 7. Quick Recovery Checklist

After any system wipe:

  1. Install Bitfocus Companion v4.1.3.

  2. Create C:\Tools.

  3. Copy the following files back in (attached):

    • Fire_KickCameraControl.ps1

    • Fire_KickCameraControl.vbs

    • Start_Companion_Hidden.vbs

    • CompanionConfig.companionconfig

  4. Import the Companion configuration file (Section 4).

  5. Verify HTTP API settings (port 8000 / bind 0.0.0.0).

  6. Restore the two Startup shortcuts (Section 5).

  7. Reboot once and confirm success in KickCameraControl.log.

Print Article