lucianoandClaude Opus 4.8
1a66a46b1f
Root cause of 'track does not start': the server re-broadcast incoming frames as binary (Buffer), so the browser output page received Blobs, JSON.parse failed, and every command (playTrack, etc.) was silently dropped — only the text-encoded lastEffect sync got through. Broadcast as text now; net.js also handles Blob defensively. Also: no-store for app assets + kiosk --disk-cache-size=1 so redeploys always take effect; /api/clients debug endpoint; /api/peaks duration. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
16 lines
646 B
Bash
Executable File
16 lines
646 B
Bash
Executable File
#!/usr/bin/env bash
|
|
# Launch Chromium fullscreen (kiosk) on the Pi's HDMI, pointed at the output page.
|
|
URL="${1:-http://localhost:8080/output.html}"
|
|
BIN="$(command -v chromium-browser || command -v chromium || echo chromium)"
|
|
exec "$BIN" \
|
|
--kiosk --noerrordialogs --disable-infobars --no-first-run \
|
|
--autoplay-policy=no-user-gesture-required \
|
|
--disable-translate --disable-features=Translate \
|
|
--check-for-update-interval=31536000 \
|
|
--overscroll-history-navigation=0 \
|
|
--ozone-platform=wayland \
|
|
--ignore-gpu-blocklist \
|
|
--test-type \
|
|
--disk-cache-size=1 --disable-back-forward-cache \
|
|
"$URL" >/tmp/chromium-kiosk.log 2>&1
|