Monitor Workflow
How to generate logs and WAV output for repeatable Greybound analysis.
The monitor workflow should produce a log and an audio artifact without requiring a real audio output device.
Preferred Command
target/release/greybound-cli --rig rigs/nox30-driven.json5 --input-wav "lab/references/tone3000-inputs/Brit - Guitar.wav" --output-wav target/greybound-nox30-monitor.wav --render-seconds 10 --sample-rate 48000 --period-size 16 --ir lab/references/tone3000-irs/celestion.wav --monitorThis renders the standalone Nox30 path for a bounded duration, writes greybound-monitor.log, and writes target/greybound-nox30-monitor.wav.
For a shorter verification run:
target/release/greybound-cli --rig rigs/nox30-driven.json5 --input-wav "lab/references/tone3000-inputs/Brit - Guitar.wav" --output-wav target/greybound-nox30-monitor.wav --render-seconds 2 --sample-rate 48000 --period-size 16 --ir lab/references/tone3000-irs/celestion.wav --monitorFuzz Render
target/release/greybound-cli --rig rigs/muffin-nox30.json5 --input-wav "lab/references/tone3000-inputs/Brit - Guitar.wav" --output-wav target/greybound-fuzz-monitor.wav --render-seconds 10 --sample-rate 48000 --period-size 16 --ir lab/references/tone3000-irs/celestion.wav --monitorThis renders the Muffin into the Nox30 path, writes greybound-monitor.log, and writes target/greybound-fuzz-monitor.wav.
For Muffin into the Nox30 model:
target/release/greybound-cli --rig rigs/muffin-nox30.json5 --input-wav "lab/references/tone3000-inputs/Brit - Guitar.wav" --output-wav target/greybound-fuzz-nox30-monitor.wav --render-seconds 10 --sample-rate 48000 --period-size 16 --ir lab/references/tone3000-irs/celestion.wav --monitorOverdrive Render
target/release/greybound-cli --rig rigs/minotaur-nox30.json5 --input-wav "lab/references/tone3000-inputs/Brit - Guitar.wav" --output-wav target/greybound-overdrive-nox30-monitor.wav --render-seconds 10 --sample-rate 48000 --period-size 16 --ir lab/references/tone3000-irs/celestion.wav --monitorThis renders the Minotaur into the Nox30 path, writes greybound-monitor.log, and writes target/greybound-overdrive-nox30-monitor.wav.
Expected Artifacts
greybound-monitor.log: text analysis stream used by the log-analysis agent.target/greybound-nox30-monitor.wav: mono WAV render at the engine sample rate.target/greybound-fuzz-monitor.wav: mono WAV render for the Muffin Nox30 rig.target/greybound-fuzz-nox30-monitor.wav: mono WAV render for the Muffin Nox30 rig.target/greybound-overdrive-nox30-monitor.wav: mono WAV render for the Minotaur Nox30 rig.
The WAV artifact is useful because it can be inspected later even when the test environment has no audio device.
Interactive Monitor
For live or device-output runs, --monitor opens a terminal monitor instead of appending a new line per refresh. The monitor keeps writing greybound-monitor.log for analysis and also exposes live amp controls:
Tab/Shift-Tab: select volume, bass, treble, cut, drive, presence, or sag.Left/Right: adjust the selected knob by 0.1 on the 0-10 scale.Up/Down: adjust the selected knob by 1.0 on the 0-10 scale.q: quit the standalone process.
The audio thread reads knob updates through atomics, so the terminal UI does not lock the real-time callback.
Current Known Observation
Recent monitor runs with the driven Nox30 configuration showed clean input and zero xruns, but severe output clipping at the selected output level. Treat clipping in this workflow as a model or gain-staging issue until analysis proves otherwise.
A short target/release/greybound-cli --rig rigs/muffin-nox30.json5 --input-wav "lab/references/tone3000-inputs/Brit - Guitar.wav" --output-wav target/greybound-fuzz-monitor.wav --render-seconds 2 --sample-rate 48000 --period-size 16 --ir lab/references/tone3000-irs/celestion.wav --monitor run produced a valid mono 48 kHz WAV with zero xruns and no near-clips or hard clips in the monitor log.
Log Analysis Agent
The greybound-log-analyst agent should analyze greybound-monitor.log and report:
- clipping percentage and peak levels,
- xruns or timing instability,
- input sanity,
- suspicious RMS or crest-factor values,
- concrete next debugging steps.