Release-by-release notes for Phasion Live. Multi-output, per-output resolution, MIDI / OSC bindings, audience engagement — the full shipping log.
--- Auto-update: open Phasion Live and it will offer 1.13.3 on the next update check.
Media Float layout fixes (follow-up to 1.13.1).
--- Auto-update: open Phasion Live and it will offer 1.13.2 on the next update check.
Bug-fix release for the Media Float layout system.
open -a — which, when several apps share a name (e.g. multiple "OnlyJams" bundles), could launch the wrong/duplicate copy. Fixes "every time I queue the layout it reloads the app."These fixes self-heal existing layouts on restore — no need to recreate them.
--- Auto-update: open Phasion Live and it will offer 1.13.1 on the next update check.
The CrowdCam release — the audience's phones become live cameras on your screens.
Turn every phone in the room into a camera feed on your venue displays.
phasioncrowdcam Syphon source; idle-throttles to save GPU when no cameras are on air./mashup/mix/all).--- Auto-update: open Phasion Live → it will offer 1.13.0 the next time it checks for updates.
The launch-readiness release. A deep security-hardening pass, real reliability feedback for the phone remote, an NDI audio fix, and a sweep of cloud-audience polish — everything needed to put Phasion in front of a paying room with confidence.
The biggest theme of this release. Phasion's cloud remote and audience surfaces are now hardened end to end.
/r, /join, and /recap URLs your QR codes point at: nosniff, no-referrer, and a clickjacking/plugin/base lockdown (frame-ancestors 'none', object-src 'none', base-uri 'none', X-Frame-Options: DENY).lsof-derived "is anyone actually receiving?" signal. When no receiver is connected, the renderer stops marshaling audio frames across the process boundary entirely.phasion.live domain.The "smart NDI gate" release. Major polish on the cost and clarity of NDI broadcasting, plus a sweep of overlay-sizing fixes and UI consistency.
Phasion now identifies every consumer connecting to its NDI senders and gates CPU work accordingly.
get_no_connections lingers after a receiver disconnects (~30-60s TCP timeout), Phasion cross-references lsof and trusts the OS over the library. CPU drops within ~4s instead of a full minute.The single most expensive subsystem in Phasion is NDI's BGRA readback + SpeedHQ encode (~80% of one core per 1080p60 lane). New dropdown in Settings:
Receivers interpolate missing frames; only fast cuts / strobes look juddery below 30. Operators pick the trade-off; nothing is forced.
Found and fixed a "double-amplification" antipattern across all DOM overlays (wrapper zoom × clamp(_, vw, _) font sizing was making text 50% larger at 1080p than at 720p). CDP-measured before and after — every overlay now renders at the same proportional size on any lane resolution.
#qr-overlay-dom; applyQrPosition() is the single resolution-normalizer.zoom: var(--lane-scale) wrapper that the rest of the audience overlays already had.?) — labels refreshed to match the actual bindings (FX-bar was reshuffled), added Alt+D (toggle Ops bar), Cmd+D / Cmd+Backspace (duplicate / delete edited scene).LS_VARIANT_TIERS Supabase secret so new product variants (Pro Local, Pro Cloud, Venue Local, Venue Cloud) don't require code edits. Falls back to pro for unmapped variants.execFileSync calls replaced with promisified execFile + Promise.all for parallel peer resolution. No more 150-300ms hitches every 4 seconds.0 (no cap — match visualizer rate) instead of 30. Operators who actively chose 30 keep their setting; new installs get the smoothest defaults out of the box.Settings preferences carry over automatically. If you previously configured a phantom filter list, it's preserved; the new IP-matching is additive.
Existing operators who want the new opt-in NDI cap defaults: open Settings → NDI → set "NDI rate" to "Match visualizer (smoothest, default)".
1.9.0's Phase D win (per-lane Syphon via Electron useSharedTexture) broke NDI as a side-effect: image.toBitmap() returns an empty buffer in shared-texture mode, so NDI receivers got either a still frame or all-black. 1.10.0 fixes NDI end-to-end and adds operator controls so the CPU cost only happens when a real consumer is actually watching.
Also: a Rust display sidecar for fullscreen on Sequoia (the menubar no longer leaks into your projector output), and a handful of polish fixes that surfaced during the NDI work.
The headline regression from 1.9.0 is fixed, and the feature is substantially better than it was before.
New native syphon.readbackOffscreenLaneBgra(lane) locks the lane's published IOSurface read-only and memcpys it into a Node Buffer. The IOSurface is MTLStorageModeShared, so this is a straight CPU copy from shared memory — no GPU stall, no Metal command-buffer flush. Cost: ~1.6 MB/frame at 480p, ~8 MB/frame at 1080p — only paid when NDI is enabled.
ndi.publishFrameLaneBgra now accepts a stride parameter so the addon can honor the IOSurface's padded row stride directly via line_stride_in_bytes, no tight-packing memcpy required.
854×480 (the old 480p preset) ships with IOSurfaceBytesPerRow=3456 not the expected 3416 — IOSurface aligns to 64 bytes. NDI's BGRA pipeline skewed the image diagonally when xres didn't match stride/4. Two fixes:
1. The 480p preset is now 848×480 (16-pixel aligned, 0.7% aspect delta from true 16:9 — imperceptible). The custom-resolution dialog snaps widths to the nearest multiple of 16 with a friendly notice explaining why. 2. For any non-aligned widths that slip through, the readback passes paddedWidth = stride/4 to NDI so the receiver sees the visible content cleanly + a small black bar on the right.
The NDI panel now has three checkboxes — Out 1, Out 2, Out 3 — that control which lanes get an NDI sender. All three default to OFF: master Enable starts the framework, you opt into each output explicitly. Disabling an output completely stops that lane's sender (no readback, no publish, no mDNS announce — zero CPU). The receiver count (N) shows in green next to each output when consumers connect.
When a lane has zero NDI receivers (get_no_connections polled every 30 frames), the paint bridge skips the IOSurface readback + publish entirely. With Resolume / OBS / Synesthesia subscribed, the lane publishes at full rate. Result on a 3-output rig with Resolume pulling Out 1 only:
| State | Lane 1 paint cost | Lanes 2/3 paint cost | |---|---|---| | NDI off | 1.3 ms | 1.3 ms | | NDI on, no receivers | 1.3 ms | 1.3 ms | | NDI on, Resolume on Out 1 | ~8 ms | 1.3 ms |
Some apps (NDI Tools' Virtual Input system extension, NDI Studio Monitor) auto-subscribe to any source they discover via mDNS, even when nobody's actively viewing. From NDI's perspective these are legitimate receivers — connection count goes up, frames get encoded.
To make this visible:
(N) next to each per-output checkbox tells youimmediately how many consumers are subscribed.
in one shot. Legitimate downstream tools (Resolume, OBS) reconnect within 1-2 s. Passive subscribers may not, so this is a useful diagnostic for "who is keeping CPU high?"
stop work on that lane, whether the cause is a phantom or a real consumer you no longer need.
NDIlib_send_get_tally is now wired into the addon (ndi.getLaneTally(lane) returns {onProgram, onPreview, anyActive, available}). Currently surfaced in diagnostic logs only; not used as the publish gate because most consumers (Synesthesia, OBS in non-broadcast mode) don't set tally. Available for future work.
Electron 41's setSimpleFullScreen leaves the macOS menubar visible on Sequoia, breaking a dark venue projector setup. The fix is a separate Rust sidecar binary (phasion-display) — winit + wgpu + syphon subscription — that opens an NSWindow in native fullscreen on a chosen display, subscribes to the lane's Syphon source, and paints it edge-to-edge.
In the Output Preview row, ⛶ Send to Display now spawns the sidecar. The Settings → Output Windows panel has per-output display dropdowns: pick a display per output, then ⛶ Send to N Displays spawns sidecars in parallel for everything you assigned.
The sidecar's CPU cost is small (subscribes to an existing Syphon IOSurface, no encoding) and it's bundled in the .app via extraResources so it just works after install.
If you assigned a display, then unplugged it, the saved assignment lingered — the per-row dropdown correctly showed "(no display)" but the aggregate button counted the stale entry ("Send to 2 Displays" when only one was assignable). Now the cleanup function filters out assignments whose display ID isn't in screen.getAllDisplays() and persists the cleanup back to config.
The Syphon settings panel had two confusing toggles:
Syphon path that Phase D's per-lane servers replaced. Operator observation: "I disable visualizer and it still outputs anyway" — because per-lane (phasion1/output1, etc.) keeps publishing regardless. The toggle was vestigial.
📹 Media Capture menu, which already starts/stops Syphon automatically via the media-capture lifecycle.
Both toggles are now hidden. The Visualizer subsection shows an explanation of the per-lane auto-publish behavior; the Media Capture subsection keeps the server-name input. Server names persist exactly as before.
OSRSharedTextureNotReleased warning — gracefully suppressedduring normal operation. The deferred-release ring from 1.9.0 already handles this correctly; the warning was a Chromium dev notice that doesn't affect frame delivery.
stats log (gate=N readback=N skipped=N conn=N tally=on/off) — always-on, useful for triaging perf reports.
PHASION_SHARED_TEXTURE=0 — fall back to 1.8.x's CPU bitmap pathif Phase D regresses on a future macOS / Electron release.
users keep their saved state.
discovered NDI source even when not actively used. Phasion can't tell the OS extension apart from a legitimate Resolume layer. The per-output checkboxes are the workaround; long-term users may prefer to disable the extension in System Settings → Privacy & Security → Login Items & Extensions → Camera Extensions.
and OBS consume NDI streams without setting program/preview tally. Available via diagnostic logs.
The big one. Two architectural fixes — Phase D (lane Syphon via useSharedTexture) and Phase E (overlay Syphon via useSharedTexture) — turn multi-output from a CPU-eating compromise into the default smooth path.
Measured live with three 1280×720 lane outputs running butterchurn + scene overlays, downstream consumed by Synesthesia:
| Metric | 1.8.2 (offscreen → bitmap) | 1.9.0 (useSharedTexture) | |---|---|---| | Phasion main-process CPU | 159% | 28% | | Per-lane paint cost | ~5ms | ~2ms (CIImage GPU scale) | | Downstream FPS in Resolume / Synesthesia | 57 (jittered) | 60 (rock solid) | | Resolume idle-headroom | <50fps | 96–118fps |
The 1.8.2 offscreen path still had a CPU bottleneck: every paint event ran image.toBitmap() to copy the GPU texture into a CPU Buffer, then memcpy'd it into our IOSurface, then published. With three lanes at 60fps, that path consumed ~970ms/sec of main-thread time — saturating it.
Phase D switches to Electron 41's webPreferences.offscreen.useSharedTexture. The paint event now hands us an IOSurfaceRef directly from Chromium's GPU context. A new native function (publishOffscreenLaneFromIoSurface) wraps it as a CIImage and renders into our published IOSurface via a Metal-backed CIContext bound to our command queue. Zero CPU bitmap. The "publish" step is sub-millisecond GPU work.
The win compounds across lanes. One output is roughly the same as before (both paths fit comfortably in the frame budget). Three outputs go from "barely manages 30fps on each lane while everything else suffers" to "all three at 60fps, Resolume getting more headroom than it ever had."
Settings → Syphon → Separate Overlay Output was a CPU explosion in 1.8.2: the overlay window was visible-but-positioned-off-screen, captured via ScreenCaptureKit, with a 30fps CPU pixel-readback fallback if SCKit failed to start (the common case if Screen Recording permission wasn't perfectly configured). The fallback read 3.7MB per frame via getImageData and ferried it through IPC. With three lanes already running, this saturated the system.
1.9.0 applies the same Phase D treatment to overlay: offscreen + useSharedTexture, alpha channel preserved, GPU-only publish path. The legacy SCKit overlay-window capture is retired (still available behind PHASION_SHARED_TEXTURE=0 for triage).
Enabling Separate Overlay Output now adds ~2ms of paint cost instead of exploding CPU. Resolume sees identical alpha-preserved overlay frames as before — same source name, just way cheaper to produce.
A bunch of operator-visible fixes shipped alongside the perf work:
poll panel, captions, now-playing card, and scoreboard now scale proportionally to the lane's output resolution. An 854×480 lane no longer renders the marquee font + trivia card at the same absolute pixel size as a 1280×720 lane, which had made the smaller lane's overlays look comically oversized. The new CSS --lane-scale variable is set per-lane in JS from outputHeight / 720 and the major overlays use zoom: var(--lane-scale, 1).
clobber bugs that made the operator-set output resolution and media capture resolution silently revert to defaults on next Settings open: (1) MAIN_ONLY_KEYS list in main now protects outputWidth, outputHeight, laneResolutions from renderer round-trips, (2) config-sync IPC now updates the media-output-scale DOM dropdown in secondary windows so they don't ferry stale values back to disk.
fires its own perf-update IPC at 1Hz; the pill now tracks per-lane stats and shows the lowest actual FPS across all lanes (stable text). Dot color reflects worst health ratio (capped lanes at 100% of their cap stay green). Per-lane FPS detail moved to the ops bar at the bottom.
butterchurn render p50, chromium paint cost, and idle-skip fraction. Diagnostic at a glance; tooltip for the full breakdown.
transitions or operator IPCs are in flight, butterchurn render is skipped AND the offscreen window's frame rate is ramped to 5fps. Cuts CPU during quiet stretches; wakes the instant audio returns or you touch anything in controls. Visible as "i%" in the ops bar.
used to silently show an empty list when macOS Screen Recording permission was denied. Now surfaces a copy-pasteable instruction with the exact System Settings path.
Visualizer Syphon toggle now reflects reality (Phase D path was always-on but the legacy isRunning() check only saw the old single-server). The overlay window no longer races the real lane 1 in ops-bar stats (its viz-stats reporter is gated off).
but no video stream was provided") that surfaced as an UNHANDLED REJECTION in the main process when a preview tile's getDisplayMedia raced its prepare-call — now filtered with a once-per-minute info log so other genuine rejections still surface loudly.
is the default path, the per-lane Window/Offscreen selector that shipped in 1.8.2 is gone. Existing operators who saved 'window' for a specific lane keep that override; new installs go straight to offscreen.
one-click panic flip to 480p/30fps/single-output to recover Resolume headroom. Phase D delivers that headroom by default; the panic switch is obsolete.
PHASION_SHARED_TEXTURE=0 — both lane AND overlay publish revert tothe legacy bitmap / SCKit paths. Use if a specific preset or system config produces visual artifacts under the new path. Default on.
PHASION_ENGINE_NATIVE_OVERLAYS=1 — re-enables the dormant Rustengine subprocess for the v2.0 work-in-progress native overlay primitives. Engine subprocess otherwise doesn't spawn (it had no useful work to do in shared-texture mode).
PHASION_FORCE_VISIBLE_LANE=N — debug helper. Forces a specificlane number back to visible-window mode (with DevTools accessible) while leaving others on shared-texture. Useful when isolating a visual bug to a specific preset.
---
Phasion Live is by AV Club Visuals. Run a venue. Make it weird.
A release dedicated to one big architectural addition and the polish around it: Offscreen Render Mode, a per-lane opt-in that bypasses the macOS compositor entirely and publishes butterchurn directly to Syphon via an IOSurface bridge we own end-to-end. In testing this delivered 100+fps sustained at 1080p where SCKit's window-capture path was struggling to hold 30-60.
Settings → Performance → 🧪 RENDER MODE (BETA) — per-lane dropdown to flip between two publish architectures:
renders butterchurn, macOS's ScreenCaptureKit grabs that window's IOSurface, Syphon publishes. Pays the compositor cost for every frame.
page offscreen at device pixels; a native publisher memcpys/downscales each paint into an IOSurface we created, and Syphon publishes it. Zero compositor involvement.
The macOS WindowServer compositor cost was the real bottleneck in 1.8.1 — bypassing it lets the lane sustain 60+fps even with downstream consumers doing heavy work.
to minimize.
phasion1/output1, phasion2/output2, phasion3/output3 source names regardless of which mode the lane is using. Switching modes doesn't break downstream patches.
(typically 2× on Retina because Chromium offscreen paints at device pixels) down to exactly the configured target (1280×720, 854×480, etc.) before Syphon publish.
re-opens the lane in the new mode without an app restart (~600ms total). Same Syphon source name is preserved so downstream apps don't need to re-pick.
desktopCapturer which needs a visible window). Resolume / Synesthesia / Syphon Inspector remain the source of truth.
(position, FPS cap, fullscreen display) is restored from config on each rebuild.
A clean, reusable native foundation that the offscreen path is built on:
StartNativeSpike / StartOffscreenLane in syphon_addon.mm — create an IOSurfaceRef, wrap it in an MTLTexture zero-copy, and publish via a dedicated SyphonMetalServer. Per-lane slots (lanes 1/2/3) each with their own IOSurface + Metal texture + Syphon server.
publishOffscreenLaneBuffer — accepts any paint dim and writes to the IOSurface at exactly the configured target. ~targetW×targetH memcpy-class ops per frame, fast enough at 60fps/1080p.
getMainScreenBackingScale — native getter that reads [NSScreen mainScreen].backingScaleFactor directly, bypassing Electron's screen.scaleFactor API (which returns 1 under --force-device-scale-factor=1).
forceLowDpr window-shrink retired. It was a 1.8.1-era SCKit compositoroptimization that shrunk lane windows to half their CSS dimensions, which forced DOM overlays (trivia card, QR code, scrolling text, photo carousel) to render proportionally twice as large in the smaller viewport. The new offscreen mode delivers the perf win without that downside, so the shrink is permanently off. Trivia, QR, fonts, and all overlays now render at correct sizes in both modes.
--force-device-scale-factor=1 flag auto-skipped when any lane isconfigured for offscreen mode. The flag conflicts with offscreen rendering on Retina, where Chromium paints at the real backing scale regardless of the flag.
startServerLane() when the lane is in offscreen mode, eliminating the "two phasion1's, one frozen" bug that appeared during mode swaps.
stopWindowCapture) and the prior Syphon server (stopServer) before recreating, so downstream consumers see a clean handoff rather than a still-framed prior source.
closeOutputLane(n) → 350ms pause → openOutputLane(n) so the operator only has to flip the dropdown.
window.__phasionPerf = true in viz devtools) logsp50/p99/max per render stage every 5 seconds plus a GC-pause counter. Useful for identifying bottlenecks; zero cost when off.
scripts/offscreen-runner.js — standalone Electron runner that loads the spike's test page or visualizer.html offscreen and publishes to Syphon. Used during development to validate the architecture without launching the full app.
scripts/spike-runner.js — minimal CPU-gradient → IOSurface → Syphon proofthat the publishing pipeline works without any rendering layer involved.
---
Phasion Live is by AV Club Visuals. Run a venue. Make it weird.
A polish + performance release focused on two things: making Phasion play nicely with downstream Syphon consumers (Resolume, Mad Mapper, OBS), and shipping the persistent event recap that turns your audience URL into a multi-day asset.
The biggest find: SCKit's window-capture stream was uncapped at 120Hz on ProMotion displays regardless of your FPS settings. Resolume was being flooded with frames it didn't need, burning GPU on duplicate work. The fix touches the native addon and every output handler.
at your chosen rate (default 30 fps). Native code rebuilt.
Settings → Outputs and the publish rate updates within ~2 s. No app restart.
compositor overhead from Retina/HiDPI rendering — was 16× wasted work at DPR=4.
destination display, then restores Syphon-mode res on exit.
One click: 30 fps cap on all lanes + 854×480 + single preset + 1× DPR + closes extra outputs + hides preview tile.
cycles for Resolume when you're not looking at controls.
frames, not the display refresh rate.
The URL you give the audience now outlives the event. Pro Cloud and Venue Cloud users get a recap that loads photos, word cloud results, and event content for 48 hours after you close the app.
phasion.live/recap/<slug> — photo grid,lightbox with download, find-my-photos by username.
with stats, emoji bars, top photos, and branding now persists on the cloud — identical to the local copy the operator built.
can export the full event archive as ZIP before the 48-hour expiry.
darkness detection + perceptual hash for dupe detection. Audience sees an inline warning on bad shots before sending.
privacy guarantee comes from Cloudflare, not app cleanup logic.
Same feature set within each family; cloud variants ranked higher (pro-cloud rank 2.5, venue-cloud rank 3.5) for upgrade copy. Legacy pro and venue continue to work unchanged.
local) from tier — new purchases route correctly on first claim.
phasion.live/venue-test — standalone WiFi diagnostic page operators orvenue staff can run from a phone before an event. Measures latency, jitter, bandwidth, sustained-connection drops. Verdict: "Pro Local will work" / "Use Pro Cloud" / "Network too unreliable."
the app, tier-aware copy (Pro Cloud users see "Cloud is doing its job" instead of upgrade pitches).
session telemetry (tunnel drops, photo upload failures, laptop sleep, low battery). Silent when nothing warrants a nudge.
(SCKit / PBO), bandwidth estimate, active feature flags. Cropped from Syphon output (sits in the titlebar area, never published to Resolume). Toggle via Settings → Privacy or ⌘⇧P inside the viz window.
window.prompt() path returns null silently in Electron renderers — now uses a native HTML <dialog> with W × H inputs, Enter to submit, Escape to cancel. Even-pixel rounding for Syphon chroma compatibility.
updates every per-lane cap. Per-output dropdowns override per-lane. No more silent override race when you set conflicting values.
The End-the-Night recap slideshow now fans to every open output, not just lane 1. Plus fixed a DPR clamp mismatch that was causing the recap to draw into only the upper-left ~67% of the canvas on DPR=3 displays.
phasion.live/recap/<slug> recap surfacephasion.live/venue-test diagnostic surfacePro Cloud comparison table
IPC for the 🪟 ops chip
---
Phasion Live is by AV Club Visuals. Run a venue. Make it weird.
v1.8.0 — Pro Local architecture (audience direct to your Mac)
The biggest release since v1.7's stable audience URL. Introduces the dual-architecture (Pro Local + Pro Cloud) split, hardens the cloud relay against the Codex audit findings, and gives operators much better visibility into what's happening under the hood.
═══════════════════════════════════════════════════════════════════ NEW: Pro Local architecture (zero cloud hop for audience traffic) ═══════════════════════════════════════════════════════════════════
Each operator can now have a stable hostname <slug>.phasion.live that routes via a Cloudflare named tunnel DIRECTLY to their Mac. No Durable Object hop, no R2 photo buffer, no cloud retention of any audience content. The architecture itself becomes the privacy story.
• New Worker endpoints (provision/deprovision/get-token) that create + manage Cloudflare named tunnels via the CF API • Tunnel tokens encrypted at rest in D1 via AES-GCM with a Worker secret (PHASION_TUNNEL_ENC_KEY) • Idempotent provisioning with auto-recovery from orphan CF resources (codes 1013 + 81053) • Operator app boots, claims slug, reads mode='local', fetches encrypted token, runs cloudflared tunnel run --token <stored> • Cloud transports (WS / SSE / Remote-SSE) skip startup in Pro Local mode — saves DO duration entirely • Audience HTML auto-detects subdomain pattern and uses location.origin for API calls (works in both cloud + local) • Operator local server gains /join route serving audience HTML, plus /state + /api/join/<slug>/<verb> path aliases so the same HTML works whether served from phasion.live/join/<slug> (Worker) or <slug>.phasion.live/join (named tunnel) • Recap pages work in Pro Local mode unchanged (served by local server via tunnel — no Worker involvement) • Daily cron sweeps orphan tunnels (failed teardown / cancelled customer) after 7 days of no heartbeat
═══════════════════════════════════════════════════════════════════ Hardening (driven by Codex pre-launch audit) ═══════════════════════════════════════════════════════════════════
• Slug validation moved upstream of DO instantiation — fake sids can no longer DoS our DO quota • RemoteSession passphrases persist to DO storage (handlePublish now fails closed when no passphrase configured) • Per-slug auth-failure rate limit (10 failed pp attempts in 5min → 429) defends against brute-force on 4-digit passphrases • DO idle alarm reads lastActivityAt from storage (was racing against the constructor's freshly-set value, re-arming forever) • handlePublish now counts WS subscribers before declaring "no subscribers" — fixed a regression where v1.8 WS operators got dropped POST commands • Cached-token revive path now calls _startAllTransports (was only restarting SSE+heartbeat, missing WS+remote — the exact cost regression v1.8 was designed to prevent) • Sleep guards added to all reconnect schedulers so close handlers triggered by suspend don't queue exponential-backoff timers • Bundle ID rename: com.avclubvj.app → live.phasion.app (helper bundle stays at com.avclubvj.app to preserve ShazamKit registration) • R2 cleanup paginates (list() caps at 1000 objects — without pagination, slugs with >1000 photos left an orphaned tail) • Photo filenames now include a per-photo suffix so concurrent submissions in the same second don't collide • Queue caps (PENDING_AUDIENCE_MSG, WC_REVIEW) prevent runaway moderation queues on long-absent operators • Word-cloud session disk writes debounced (500ms) — a flurry of 50 phones submitting in 2s used to do 50 fs.writeFileSync calls • Renderer crash counter is now a 10-min sliding window (was cumulative — 3 GPU hiccups over an 8hr gig used to brick auto- respawn forever) • Delta queue cap (200 items) prevents OOM during stuck WS flushes • NDI audio publishing gated on hasAnyReceivers() • Latency-beacon endpoint rate-limited + slug-validated
═══════════════════════════════════════════════════════════════════ Operator UX ═══════════════════════════════════════════════════════════════════
• Ops bar (⌥D): new TUN dot for tunnel health + 📱 phone counter (live SSE subscribers, amber at 200+ for Pro Local capacity) • Plain-English tooltips on every ops-bar item explaining what the channel is, why you'd care, and what its current state means • Mode-indicator chip in Submission Link section: tells operator whether they're on Pro Local (📡) or Pro Cloud (☁️) with a one- line architecture summary • Periodic transport re-sync (every 10s) self-heals any IPC race where the ops bar got stuck on a stale "disconnected" badge • Diagnostics bundle exports operator state as a single JSON file via Settings → Privacy → "Save bundle…" — includes Pro Local / Pro Cloud architecture summary, current tunnel status, audience phone count, recent breadcrumbs (sensitive fields redacted) • Cloud-status reason cell surfaces human-readable explanations when transports degrade ("Audience cloud is busy — retrying. Local tunnel still works.") • End-the-night cleanup: stops running activities + drains pending moderation queues + wipes R2 audience content at 4am rollover • FX strip pruning: removed SHAKE/ZOOM/CRUSH/BLUR (4 low-impact glitch effects per operator feedback). HUE moved next to FLASH
═══════════════════════════════════════════════════════════════════ Marketing site ═══════════════════════════════════════════════════════════════════
• Pricing page restructured into 4 tiers: Pro Local ($19), Pro Cloud ($49), Event Pro ($99 one-month), Venue ($499/yr) • Privacy page split into per-mode sections — Pro Local now carries the real claim "photos never leave your Mac" • Features page audience section calls out the Pro Local / Pro Cloud distinction with the privacy-by-architecture pitch • Homepage AT YOUR EVENT card mentions both architectures • Pricing page Lemon Squeezy checkout URLs reserved for new SKUs (real product IDs wired in when you finalize prices) • Recap pages, features images (output_routing, qr_code, branding, midi, visuals video) all live
═══════════════════════════════════════════════════════════════════ Migration ═══════════════════════════════════════════════════════════════════
D1 migration 0006_slug_tunnel.sql adds tunnel columns to slug_registry. Apply once with:
npx wrangler d1 execute phasion-trials --file=./migrations/0006_slug_tunnel.sql --remote
New Worker secrets required for Pro Local provisioning: CLOUDFLARE_API_TOKEN, PHASION_LIVE_ACCOUNT_ID, PHASION_LIVE_ZONE_ID, PHASION_TUNNEL_ENC_KEY
Existing customers default to mode='cloud' on first license check post-upgrade. No action required for cloud-mode operators.
Polish + bugfix release on top of v1.7.0 phasion.live. Also bundles the WebSocket migration of operator state push + remote control commands (was developed against 1.7.0 but never cut as its own release).
idle traffic to ~0/min.
/r/<slug>) and moderator (/mod) commands also moved to WebSocket — no more per-click POST to /cmd.
if a Worker redeploy zombies the SSE/WS.
per operator feedback. MIDI mappings to those keys are silently dropped from existing configs (harmless).
1 = SPIN, 2 = SQUEEZE, 3 = RIPPLE, 4 = HUE, 5 = BLACK1=ZOOM, 2=CRUSH, 3=BLUR, 4=SPIN, 5=HUE fireAt timestamp and each visualizer waits until that instant before firing. Eliminates the visible 1-2-3 ripple of FX across multi-output lanes.
16px empty space below them.
toggle is off. Previously the box stayed visible even though the remote server was loopback-only and the LAN IP was unreachable.
This is the big one. No more random tunnel URLs that change every show. Every install now gets a stable phasion.live/join/<slug> URL that the audience scans, plus a phasion.live/r/<slug> remote-control URL the operator's phone bookmarks once. Both work without a tunnel, both survive app restarts, and venues get the option to claim a custom vanity URL.
phasion.live/join/<slug>Every licensed install (Pro / Trial / Venue) auto-claims a 4-character slug on first launch. The audience QR encodes that URL forever — no more re-sharing a new link every night. Same QR poster works in week 1 and week 52.
phasion.live/join/k7f2).phasion.live/join/bluemoon-bar). Settable from the QR menu → More options.The full audience-submit page (messages, photos, AI prompts, emoji applause, word cloud, polls, trivia, photo contests, caption contests, white-label branding) is hosted at phasion.live with feature parity to the previous github.io page. The legacy github.io URL is dropped from the QR menu — phasion.live is the canonical audience URL going forward.
phasion.live/r/<slug>The same slug your audience scans is reused for your operator phone remote. Bookmark phasion.live/r/<your-slug> on your phone once, and every session-start auto-pairs. No more "find your local IP, type it manually."
phasion.live/mod page reached by entering the moderator passphrase instead of the operator one. Same QR — different password → different page. Mod commands are server-side gated against MOD_ALLOWED_CMDS so a leaked mod token can't change scenes, kill audio, etc.If you launch the app without signing in, you still get a fully functional phasion.live/join/<slug> URL bound to your device fingerprint. Watermark stays on (same as before), but every audience-engagement feature works. When you later sign up, the app issues a fresh license-tied slug and the anonymous one frees up.
Operators on the Venue tier can upload a logo + accent color + custom copy in app settings. That branding now also flows through phasion.live — the audience page renders your venue's look with the logo inlined as a data URL (no extra fetch). Changes propagate in under a second via SSE.
The multi-output mashup buttons now read Change All, Same All, Fade All instead of just Change, Same, Fade — clearer that they hit every open output.
{prompt, name, photoDataUrl?, photoWeight?} and the relay was looking for {text, username}. Fixed.onmessage handler. Fixed by stripping the event: header so all events flow through one dispatch path./react route's behavior (one random lane per react)._applyOperatorBranding() prepended the API base to any URL not starting with http. Data URLs got broken into /api/join/<slug>/data:image/png;base64,.... Fixed to recognize data: as already-absolute.slug and voterId fields from photo submissions. Now preserved end-to-end so contest photos route to the right activity.state events coalesce (latest wins, idempotent), delta events queue separately so wordcloud submissions / vote events / live-updates are never dropped.marketing-site/phasion-link.js) handles slug claim/refresh/reset, license-signed auth, audience submissions, operator state mirror, and the new AudienceRelay Durable Object that holds the SSE stream per slug.subscription_cancelled / subscription_expired / order_refunded events and sets license_expired_at on the slug row so the audience page shows the "subscription expired" UI.corunography.github.io/avclubvj/?t=...&w=... audience URL still works for installs already running it, but is no longer surfaced in the QR menu. All new submissions flow through phasion.live.Per-output resolution + grid-preview reliability + a top-bar redesign. Each audience display now has its own publish resolution (720p / 1080p / 1440p / 4K / Custom), locked to the configured size. The "Preview: All" grid no longer leaks Output 1's stream as a backdrop behind the other tiles. And the top-bar mashup controls got cleaned up: thinner duration dropdown, a numeric mix readout, removed clutter (Speed / Auto / legacy global resolution dropdown), and a responsive layout that fits all your buttons inline at multi-col widths and reflows cleanly at narrow widths.
Each output now has its own publish + window size, settable independently from Settings → Output Windows. The Output 1 / 2 / 3 rows now show a resolution dropdown next to the display picker and the Windowed / Fullscreen toggle.
phasion1, phasion2, phasion3) publishes at its own lane's native resolution.canvas.width for its sizing math, so each lane's overlays render at the right size for that lane's resolution. A 1080p output and a 720p output running the same scene look visually identical, just at different pixel densities.The 1.6.0 multi-output release shipped with Output 2 and Output 3 windows being freely draggable / resizable. That looked harmless, but SCKit window-capture scales the captured frame to the configured publish dims — so dragging Output 2 down to, say, 800×600 left Syphon publishing a 1280×720 stream that was an upscaled blur of the smaller window. The lock here makes the captured frame match the rendered frame exactly.
When "Preview: All" was active, Output 1's single-tile capture stream stayed running in the background, visible as a backdrop behind the per-lane grid tiles. Operators were toggling Preview Active → Preview All to manually clear it. Root cause was an async race between applyVisibility() (which manages the single-tile preview) and _startGridImpl (which manages the grid). Three layers of fix: 1. applyVisibility now reads a gridActive flag and forces the single-tile stream off when grid mode is showing multiple lanes. 2. _startGrid and _stopGrid proactively trigger applyVisibility so the gate evaluates the instant grid state changes (instead of waiting for the next matchMedia / tour event). 3. The async startStream() re-checks gridActive after the getDisplayMedia await resolves and abandons the in-flight stream if grid mode flipped on mid-await — preventing a zombie capture from binding to the hidden mainVid element.
Patterns 3 (H-Split), 4 (V-Split), 6 (Radial), and 9 (Luma key) had their slider direction inverted relative to Crossfade and Noise wipe — at slider left, the user saw preset B instead of preset A. All five patterns now share the same direction:
overflow: hidden rule no longer leaks into Settings).@media (min-width: 1100px) grid template).The Visual Mix top-bar got a layout overhaul to use space more wisely at every width:
0.50) on the right edge so you can tell when it's centered without eyeballing.padding-bottom on the collapsed .section-body.The "📐 Syphon Position Adjust" sub-section in Settings → Output Windows is now hidden by default — the per-lane SCKit crop math has been stable for several releases and the manual offset sliders weren't being touched. Inputs stay in the DOM as stubs so existing handlers don't error; the section can be re-enabled by removing one style="display:none" wrapper if a future SCKit regression makes manual adjust necessary again.
Existing 1.6.x users pick this up automatically on the next "Check for updates". After installing, restart Phasion Live. Your existing single global resolution is preserved as Output 1's default; Outputs 2 / 3 inherit the same dims initially but can now be changed independently via Settings → Output Windows.
config.laneResolutions = { "1": {w,h}, "2": {w,h}, "3": {w,h} } storage. Falls back to the legacy global outputWidth/Height for installs without per-lane entries, so existing setups continue to work without re-configuring.set-lane-resolution(lane, w, h) IPC: resize window → push new resolution to renderer → restart SCKit capture at new dims. Lane 1 also routes through here for consistency, while the legacy set-viz-size IPC keeps working as a shortcut.did-finish-load re-pins setContentSize(w, h + 28) defensively so the captured frame is exactly the configured dims from the first publish (matches how Lane 1 already did it).useContentSize: true + resizable: false on lane construction — both belt-and-suspenders against accidental drift.flex-wrap: nowrap at multi-col widths (≥740px) + JS re-parenting at narrow widths (<740px) so the master gang lives in different DOM positions for the two layouts without duplicating any elements.Hotfix. Lane 1's Syphon server (phasion1) was publishing Lane 3's content in some multi-output sessions. This release fixes the routing.
In 1.6.0, the SCKit window-capture used to feed Lane 1's Syphon server (phasion1) matched windows by substring — searching for any OS window whose title contained "Phasion Live — Output". Lane 2 and Lane 3 use titles "Phasion Live — Output 2" and "Phasion Live — Output 3" — both of which contain that substring.
Depending on the order SCShareableContent returned windows on a given boot, Lane 1's capture could lock onto Lane 3's window instead of Lane 1's. Result: downstream apps (Resolume, Synesthesia, OBS) saw phasion1 publishing whatever Lane 3 was showing — and phasion3 showed the same thing because it correctly bound to Lane 3.
The lane 2/3 path already used exact-match (isEqualToString:) for window lookup; only Lane 1 was using the loose substring match. This release equalizes the matching logic so every lane's Syphon server is guaranteed to publish its own lane's content.
Why this manifested only in the packaged build but not in npm start: pure SCKit window-enumeration ordering luck. The bug was latent in both — in dev, lane 1's window happened to be returned first; in the packaged build, lane 3's was. Same code path, different order.
Existing 1.6.0 users pick this up automatically on the next "Check for updates". After installing, restart Phasion Live and test with Resolume / Synesthesia: each of phasion1, phasion2, phasion3 should now publish its own lane's content.
Multi-output. One Phasion install can now drive up to three independent audience displays — different scenes, different presets, different feeds — from a single controls window. This is the biggest update since Phasion Live shipped.
setActiveLane1/2/3, laneNext, lanePrev (MIDI notes or CCs) and /lane/active <n>, /lane/next, /lane/prev (OSC).mashupChangeAll, mashupSameAll, smoothFadeAll, mashupRandomBothActive (MIDI) and /mashup/all/{change,same,fade}, /mashup/random/ab/active (OSC)./lane/active/state <n> on every focus change so TouchOSC layouts can light up an "active output" LED.The phone-served remote control page (http://<lan-ip>:3131/) now shows:
▸ ⚡ VISUAL EFFECTS to expand. Saves ~86px of vertical space for operators who drive FX via keyboard / MIDI.The onboarding tour now reads body[data-license-tier] and filters its 26 steps to match what the operator can actually do:
A non-exhaustive list of bugs squashed across this release:
vizWindows from main rather than its own stale module state._activateCue awaits before committing its lane filter, eliminating the race._pendingFTBConfigByLane Map + lane-tagged midpoint IPC routes each lane's pending config to the correct apply path. Multi-output bursts now honor the configured transition style (random / wipe / dissolve / zoom / glitch) on every lane._wcClearTestSubmissions no longer fires an unconditional _wcMenuPushLive, fixing the rare flash of Open Mic overlay during a scene-to-scene transition right after activity exit.activateFeed() now captures the LANE's previous feed up front and gates its teardown IPCs on that, so a lane-2 burst clearing the global flag doesn't strand a carousel running on lane 1.overflow: hidden was leaking into Settings windows, clipping the tail of long sections (Branding, Privacy). Settings now correctly scrolls.phasion1, phasion2, phasion3 so downstream apps (Resolume, etc.) can address them individually.open-output-lane, close-output-lane, list-open-lanes, output-lane-opened, output-lane-closed.remote-state-active-lane, remote-state-recompute-lanes. Lane focus on the desktop pushes via pushSSE so every connected phone repaints its tab strip within ~100ms.shared.toVizLanes is now a lane-aware fan-out: messages with lane: N route to that lane only; messages without lane fan to every open lane.Existing 1.5.x users pick this up automatically on the next "Check for updates" via the in-app updater. After installing, restart Phasion Live to load the multi-output substrate.
The audio-reactive engine itself is still butterchurn. Multi-output runs three independent butterchurn pipelines side by side — each consuming the same audio analyzer, each producing a fully independent render. No shared GPU state between lanes, no preset cross-talk. Your existing presets, custom themes, scenes, setlists, and branding overlays all work without change — they're now just multi-output-aware.
Patch release — fixes a broken pricing link in the trial-expired modal.
When the 10-minute free-trial timer fires in v1.5.5, the modal's "See pricing →" button pointed at phasion-live.pages.dev/pricing.html — a Cloudflare Pages project that was retired shortly after 1.5.5 shipped. Result: trial users clicking through to upgrade hit a 404 instead of the pricing page.
This release re-targets that button at the live marketing site (phasion-live.corunography.workers.dev/pricing.html).
No other behavior changes — same 10-minute trial, same modal, same Quit button, same all-other features as 1.5.5.
Existing v1.5.5 users will pick this up automatically on the next "Check for updates" via the in-app updater.
10-minute free-trial timeout and a refreshed pricing flow.
Unlicensed sessions run for 10 minutes from app launch, then freeze. This matches the in-browser trial at https://phasion-live.corunography.workers.dev and gives prospects a clear "you've seen what it does, here's the upgrade" moment instead of a permanently watermarked free product.
unlicensed or signin_needed — licensed/grace sessions never see it./pricing.html — Free / Web ($30/yr) / Home ($60/yr) / Pro ($19/mo, $190/yr annual) / Venue tiers, with a Monthly ↔ Annual toggle on Pro./try/ browser-based trial with the same 10-minute cap as the native app, dual-preset blending, audience-display popout, 1,144 base presets + 14k bonus presets loaded from R2 storage./try/ — A/B/S for slot randomize + swap, arrow keys for blend + sensitivity, F for fullscreen, ? for the help panel.app:quit so the controls renderer can request a clean shutdown.to-viz channel gets a new message type trial-expired which cancels the rAF chain in visualizer.js and tears down audio capture./try/ fetches it cross-origin and caches in IndexedDB for return visits.Pick a mood per slot via a tiny inline dropdown next to each ⚡ Gen button: 🧊 Calm · ⚡ Aggressive · 🌀 Psychedelic · 📐 Geometric · 💧 Liquid · 💥 Strobe · 🎭 Hybrid · 🎲 Random. Mashup any two moods (Calm × Strobe!) by setting different styles per slot. Default 🎲 Random rolls a fresh mood each click so generations look distinctly different, not slight variants of each other.
Pulls frame_eqs from one preset and pixel_eqs from another. Real butterchurn JS recombined — always compiles, never the same chimera twice.
Now retries up to 3 times if a generated preset fails to compile, and stops the spinner immediately on total failure instead of waiting for the 30s safety fallback. Previously about 20% of clicks would silently no-op.
The backdrop-filter compositor layer is now pre-warmed at parse time (same pattern as the QR overlay). The GPU doesn't rebuild it on each Shazam match — no more visible hitch when a song appears on screen.
Defensive stop+drain in startMediaCapture, proper Phase 4 ordering after the boot preset apply, and a guard against double-mediaStart. Eliminates the intermittent SIGSEGV on launch when a preset's auto-restart raced with the async restore IIFE.
Activating scenes that previously baked beatSyncEnabled:false no longer flips your global toggle off. Live BPM also visible in the header next to FPS while Beat Sync is active. Photo-carousel counter follows the same pattern.
One-time dedupe-by-name on launch keeps your customised originals.
---
Direct download (always latest): Phasion-Live.dmg
A new PACK dropdown above the category selector in the AI Visuals section. Pick a themed pack to override Roll and Auto-cycle — they'll now draw from the pack's prompts instead of the category engine. Ships with a built-in 🤖 AI Visuals pack of 20 starter prompts (psychedelic / cosmic / surrealist / artist-style), and the Pack creator in Stage Management → Prompt Packs gains a 🤖 AI Visuals option so you can author themed packs for specific events.
Crops applied from a saved preset now snap in immediately on launch — no slider nudge required. The root cause was window.devicePixelRatio briefly returning 1 before Electron settled the Controls window on its display, then becoming 2. That meant the first sendCropUpdate after launch shipped half-scaled crop values, and any later nudge shipped double-scaled. Hardcoded the scale so it can't race.
Switching a saved preset across monitors mid-session no longer requires a manual Restart Capture. applyMediaCropPreset now auto-cycles the SCKit stream (500ms settle) so the bitmap context re-binds to the new display's frame dimensions. Per-monitor presets stay valid since each one's stored slider values are still calibrated to that monitor's source frame.
Prompts in the pack editor textarea now have a blank-line separator between them so long prompts no longer blur into a wall of text. Larger font, more line-height, refreshed helper copy.
---
Direct download (always latest): Phasion-Live.dmg
start-audio immediately when previously connected. Before: dropdown change reset the badge but the old device kept streaming until you clicked Connect again. Fixed.preload.setMediaEnabledSync now actually uses ipcRenderer.sendSync. Previously it was async-aliased, so the renderer's quit-time write didn't complete before main flushed state to disk. The "I enabled it but it forgot after restart" bug is fixed.On launch, the crop sometimes doesn't visually apply until you nudge a crop slider by 1 pixel. The ⟳ Restart button is a one-click workaround. We have an open investigation into this — the root cause is in the native syphon addon's binding behavior that we don't have source access to. Tracking for a future release.
Apple-Silicon Macs only. Direct DMG download. Signed and notarized.
Same crop slider values now produce identical framing in both the Phasion Output window AND any Syphon receiver (Synesthesia, Resolume, OBS Syphon, etc.). The on-screen display canvas had a hardcoded "+21 src px top, +23 src px bottom" compensation baked into its render loop; it's been removed. Calibration is once-and-done.
start-audio immediately — before, the badge changed to "disconnected" but the previous device kept streaming until you clicked Connect again.Apple-Silicon Macs only. Direct DMG download. Signed and notarized.
renderCaptionModels call fired lyrics-disable to the shared visualizer.default-engine — minimal preset designed for the Engine tier.Apple-Silicon Macs only. Download the DMG, drag to Applications. Signed and notarized.
Bug fixes:
Bug fix:
Electron 41, 2-col responsive layout, Metal Syphon preview, photo pipeline overhaul, friendly link labels, clean-shelf launches
Three UX fixes that landed after a stream-of-consciousness pass through the controls window.
!important, making them slab against the pale page chrome in light mode. Light-mode overrides now win the cascade with white fill, neutral grey text, and a soft red active-state for the ISF toggle buttons.#8a8a90 → #6a6a70) — readable as "the dark one" without slabbing pure black against the rest of the row. Press / strobe-flash still goes to true black for the active feedback moment.The new build also strips legacy persisted collapse-state keys from venue.json on first launch (collapsedSections, collapsedMenuGroups, collapsedModSections, etc.). They're all unused now.
Big perf win on the controls-window launch path.
A DevTools performance trace caught the controls window racking up ~30 layout shifts and a 0.66 Cumulative Layout Shift score during the first ~1.4 s of every launch. Cause: the section / menu-group / mod-section initializers each apply the .collapsed class to many elements at once, triggering all their max-height / margin-top / opacity transitions to fire simultaneously on a 9k-element DOM.
The fix:
<body> boots with a .no-transitions class that disables every transition + animation on every descendant..no-transitions is active, so their forced layouts don't compete with the init burst.LCP is bounded by the dev/Webpack bundle parse + synchronous init code; further wins would require code splitting, deferred for now.