jens/docker-dosbox-novnc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Note audio streaming should be shared across noVNC-family projects

Browse Source 
Follow the common/scripts/signals.sh precedent: build the browser
audio + noVNC piece project-agnostically in common/, then copy it into
each project's own scripts/ rather than making it dosbox-specific.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NiNnj78HGx1KWyCCo39HSz
This commit is contained in:
jens
2026-07-28 10:49:02 +02:00
co-authored by Claude Sonnet 5
parent 568c284a8a
commit 2c70def189
1 changed files with 7 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
TODO.md
+7
View File
@@ -49,3 +49,10 @@
browser side, feed them straight into the Web Audio API via an `AudioWorkletNode` (not browser side, feed them straight into the Web Audio API via an `AudioWorkletNode` (not
`<audio>`, not `ScriptProcessorNode` — that's deprecated and has worse latency) for `<audio>`, not `ScriptProcessorNode` — that's deprecated and has worse latency) for
near-real-time scheduled playback. No container/codec framing in the path at all. near-real-time scheduled playback. No container/codec framing in the path at all.
Build this to be reusable across the other noVNC-family projects (`docker-xserver-novnc`,
`docker-sdr-novnc`), not dosbox-specific — it's a "browser audio + noVNC" concern, nothing
about it is really about DOSBox. Follow the `common/scripts/signals.sh` precedent: keep the
generic PulseAudio-sink/WebSocket/AudioWorklet piece project-agnostic in `common/`, then copy
it (not symlink) into each project's own `scripts/` the same way signal handling is shared,
so a fix in one place gets propagated by hand to the others.