~ knotless Search/
↑↓ move↵ open⇧↵ all results

cameron.stream/prism

Audio-reactive WebGL visualizer for OBS streams

0
0
main
Go to filet
Code
README.md

Staged next visualizer — NOT LIVE

Do not modify ../index.html, ../server.cjs, or restart the live :4178 server while the owner streams. Their hashes at staging start:

  • index.html e427014bbf62a38651f62420eb9558cc6141f6d8057b98930ed631a69c88f98c
  • server.cjs 0c3fd365ad56a798db57b534b5023f7497f0165f23fee460a8fc01752bc55de4

Owner shares only ONE fixed URL http://127.0.0.1:4178. Staging port 4180 is loopback test infrastructure only, not a replacement share link. Switchover needs explicit permission after the stream. Do not open staging on the owner's desktop without asking.

New direction: sculptural braided prism ring, near-black idle glass, audio-driven expansion and deformation, chromatic spatial dispersion, internal specular caustics, frame-rate-independent light memory, broad restrained glow, transient wavefronts. No text, photos, visible controls, or background imagery. Bottom crescent is an audio-only witness. Fixed dB map -58 to -10dB, no artificial auto-gain; frames stop receiving energy after 700ms without data. Keeps slow ambient precession but intensity and deformation follow real data.

New server uses built-in Node WebSocket to subscribe read-only to OBS InputVolumeMeters (65536), specifically macOS Audio Capture, currently set to Ableton Live. It never calls source-property enumeration, never changes OBS settings. Reads OBS password from its existing local config, never outputs it. Emits RMS and peak only, NOT spectrum — shader history is amplitude history, not fabricated frequency data. Reconnects automatically. Live microphone and other sources are ignored. This depends on OBS's existing source staying configured/unmuted appropriately; input meters can show signal even if OBS mutes a source.

Staging bridge actually observed nonzero Ableton data: rms .0132593261, peak .0323665328. Browser smoke test at 960x540 got valid OBS events but Ableton was silent during that test. Controlled test (explicitly synthetic, test browser only) rms .06 / peak .15 produced energy .61693 and peak .77044; after stopping samples energy decayed to .001747 in 2.2s. No JS errors; no visible body text. Screenshots preview-active.png / preview-idle.png. Early empty-region rejection added to shader.

Performance: headless Chrome smoke ~26–27fps at 960x540 while owner streams. Do not claim 60fps or full-resolution validation. Needs profiling, likely fewer filament samples / lower render cap before switchover. Browser render cap currently1440x900, which may be too high. No deployment performed. Next server running job_4c987bd092. Run node server.cjs (no timeout) in this directory if needed. /health exposes only latest meter reading/status on loopback.

Future deployment options: replace live server with next bridge when owner authorizes restart, preserving :4178 via PORT=4178; change main scene only after permission. Current live server has automatic HTML reload, so even changing ../index.html interrupts the live view. No auto-reload is included in next staged HTML.