Greybound
Development

Development Workflow

Commands for validating Rust code, monitor output, and the Fumadocs site.

Rust Checks

cargo test -p greybound
cargo test -p greybound-cli

Monitor Render

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 --monitor
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 --monitor
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 --monitor

Expected outputs:

  • greybound-monitor.log
  • target/greybound-nox30-monitor.wav
  • target/greybound-fuzz-nox30-monitor.wav
  • target/greybound-overdrive-nox30-monitor.wav

Docs

From the docs directory:

npm run dev
npm run build
npm run typecheck

Use the docs to record the state of the system as part of the implementation, not only after implementation is complete.

State Ledger

Decisions and open questions that should steer upcoming implementation.

Contributor Guide

How to understand the project and make changes without losing engineering context.

On this page

Rust ChecksMonitor RenderDocs