- HTML 74%
- C# 15.1%
- C++ 8.1%
- Python 0.9%
- Rust 0.8%
- Other 0.8%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| audio_field | ||
| calibration/targets | ||
| config | ||
| docs | ||
| faust | ||
| localcast | ||
| native | ||
| notes | ||
| research | ||
| scripts | ||
| state | ||
| tests | ||
| tools | ||
| .gitignore | ||
| AGENTS.md | ||
| README.md | ||
| requirements-calibration.txt | ||
LocalCastBridge
LocalCastBridge turns the local streaming rig into synchronized OBS-facing program output. The old SRT bridge is compatibility scaffolding; the target machine is Aquarium GPU fusion plus Faust DSP over one five-second reservoir.
Start with docs/perfect-machine.md for the live architecture.
V1 does not fork OBS. OBS already accepts SRT Media Sources, and FFmpeg can capture Windows desktop/audio while encoding video with h264_nvenc. The sane first machine is:
flowchart LR
A["Husband's PC"] --> B["FFmpeg capture scripts"]
B --> C["NVENC H.264 video over SRT"]
B --> D["Opus audio source 1 over SRT"]
B --> E["Opus audio source 2 over SRT"]
C --> F["OBS Media Source: video"]
D --> G["OBS Media Source: audio source 1"]
E --> H["OBS Media Source: audio source 2"]
The video stream is encoded on the sender. Audio sources are separate endpoints so OBS can mix, mute, filter, and monitor them independently.
Audio Field
The expanded rig has a separate audio-field spine for six microphones and two calibration speakers. Start with docs/audio-field.md and config/audio-field.example.json.
That path is stricter than the OBS endpoint path: microphones feeding the Ambisonic field need one synchronized capture device, explicit geometry, and calibration before they become an AmbiX FOA bus. Separate USB microphones can still be investigated, but they do not get waved through as a coherent field just because the JSON is feeling brave.
Current Status
This repo is the first coherent scaffold: architecture docs, persistence machinery, and Windows scripts for device discovery, config validation, and FFmpeg command generation. It is ready for a real two-PC smoke test once FFmpeg with SRT/NVENC support is installed on the sender.
Quick Start
- Install OBS on the receiver.
- Install FFmpeg on the sender, with
srtprotocol andh264_nvencencoder enabled. - Copy
config/localcast.example.jsontoconfig/localcast.json. - On the sender, list capture devices:
.\scripts\sender-discover.ps1
- Edit
config/localcast.jsonwith the receiver IP and chosen DirectShow audio device names. - Dry-run the generated FFmpeg commands:
.\scripts\sender-start.ps1 -Config .\config\localcast.json -DryRun
- Start the sender:
.\scripts\sender-start.ps1 -Config .\config\localcast.json
- In OBS on the receiver, add one Media Source per URL from
docs/obs-receiver-setup.md.
Why SRT Media Sources First
OBS documents SRT playback through VLC Source or Media Source, and Media Source can listen on srt://0.0.0.0:PORT?mode=listener&timeout=5000000 with mpegts input format. FFmpeg also documents SRT protocol support and Windows capture devices through dshow/gdigrab. That gives us a standard, inspectable path before native OBS code starts making expensive promises.
Repo State
Rehydrate with the bundled Python from this Codex workstation, or any normal Python 3:
& 'C:\Users\Meta\.cache\codex-runtimes\codex-primary-runtime\dependencies\python\python.exe' .\tools\localcast_state.py status
Get-Content .\state\map.yaml
Get-Content .\notes\fresh-workspace-handoff.md
Get-Content .\notes\current-system-map.md