Show-day evidence, without pretending to control the show.
SignalProof is a local-first companion for DAW-based live sets. It records the rig and checks you declare, then makes the evidence boundary visible. It does not process, route, repair, record, play, or control audio.
- Create or select a Stage Plan and complete its declared rig profile.
- Write the critical actions you must be able to perform under pressure.
- Place SignalProof Pulse in a genuinely active DAW audio path and start audio.
- Run a current foundation smoke test.
- Rehearse every declared action, verify each fallback file, and finish the manual recovery drill.
- Only when the Stage Contract says READY, write a local Stage Card.
1. Install the desktop app and Pulse bridge
| Platform | Install |
|---|---|
| Windows | Run the current x64 installer. It installs the SignalProof desktop application and the SignalProof Pulse VST3 bridge. Rescan VST3 plug-ins in the DAW after installation. |
| macOS | Verify the current ZIP checksum when a trusted SHA-256 sidecar is supplied, extract it, move SignalProof.app to /Applications or ~/Applications, and place SignalProof Pulse.vst3 in ~/Library/Audio/Plug-Ins/VST3/ or /Library/Audio/Plug-Ins/VST3/. For this unsigned field-beta build, Control-click the app, choose Open, and confirm the macOS prompt. |
Keep the desktop app open while using the bridge. Pulse is intentionally transparent: it observes real audio callbacks but does not alter the source audio, buffer, driver, device, DAW project, or routing.
2. Declare the Stage Plan
Open Home, create a plan, then save the actual rig you intend to use. The editable fields are your declaration, not automatic discovery.
| Field | What to enter |
|---|---|
| Show / plan name | A recognizable show, set, or repeatable rig name. |
| DAW / build, interface, driver/mode | The values actually selected for this session. |
| Sample rate and buffer | The current settings, such as 48 kHz and 128 samples. |
| Critical actions | One observable action per line, such as switching to a known-safe output or recalling an emergency scene. |
Refresh local options can suggest earlier local plan values and read-only local audio-device facts. You can always type another value. It never scans DAW projects or processes, changes an audio device, or treats a suggestion as verified evidence.
3. Run a foundation smoke test
- Save a complete profile with at least one declared critical action.
- Insert SignalProof Pulse on a DAW path that is actually being processed.
- Start playback or otherwise make that path active.
- Return to Home and choose Run foundation smoke test.
A successful smoke test records that the saved profile was complete, Pulse was live in this desktop session, and the local journal was healthy. It is not a performance benchmark or a certification. Closing and reopening SignalProof begins a new evidence session, so the earlier live smoke does not remain current.
4. Rehearse, verify fallback media, and run the drill
Open Rehearse and perform every declared critical action on the real rig. Mark an action complete immediately after doing it. Skipped, unknown, or interrupted actions intentionally block READY.
Add each fallback file you would genuinely use on show day. SignalProof accepts local .wav, .aif, .aiff, .flac, and .mp3 files, then records descriptive metadata and a content fingerprint. It does not copy, upload, play, edit, repair, or delete the source media.
Finally, start the manual timed recovery drill, perform the real recovery sequence, confirm the result yourself, and finish the drill. The timer records a human-run rehearsal; SignalProof never triggers fallback playback.
5. Read the Stage Contract and write a Stage Card
The contract becomes READY only when a current live smoke is present, every declared action is complete, every selected fallback item is verified, the human recovery drill is finished, and the local evidence journal is healthy.
When it is ready, choose Write local Stage Card. The card is a concise redacted handoff record: it excludes annotations, raw file paths, action labels, and media names. It captures what was checked at that time; it does not promise the future rig will stay stable.
Library, Live Mode, and support
Library can hold local action templates, setup snapshots, and historical matching profiles. Applying or restoring material deliberately resets the evidence that must be repeated. A similar profile creates a new declaration only; it never transfers smoke, rehearsal, fallback, drill, or READY evidence.
Live is a high-contrast read-only view of the current contract, Pulse state, latest verified fallback, recovery-drill state, and next safe action. Exit Live Mode before editing or running another check. A redacted support bundle is available for technical help and deliberately excludes audio, DAW projects, raw paths, action names, media names, user names, and machine names.
Troubleshooting
- Pulse is not live: keep the desktop app open, rescan VST3 plug-ins if needed, put Pulse on a genuinely active path, and make that path process audio.
- A re-test is required: save the complete profile, restore active Pulse evidence, and run the smoke test again. A rig change, restored snapshot, reset, or new app session correctly invalidates earlier live evidence.
- A fallback file fails: choose a currently accessible, non-empty file in a supported format. Reverify a file that has moved or changed.
- The contract is not READY: read the individual gate states in Rehearse. Complete the missing smoke, action coverage, fallback verification, or recovery drill instead of bypassing the gate.
- Local evidence is unavailable: do not hand-edit the journal. Back up
%APPDATA%\EgoB\SignalProofon Windows or~/Library/Application Support/EgoB/SignalProofon macOS, check storage and permissions, then restart.
Privacy and removal
SignalProof is local-first and does not require a cloud account or background network service. Uninstalling leaves the local evidence folder, DAW projects, and media untouched. Remove that folder only after explicitly exporting or discarding the evidence you no longer need.
Use SignalProof as an honest record of what was checked—and keep a human operator responsible for the live system.