Skip to content

Add experimental room-tone synthesis and opt-in repair fallback - #2

Draft
lobsterclause wants to merge 1 commit into
feat/dialogue-levellerfrom
feat/room-tone-synthesis
Draft

lobsterclause wants to merge 1 commit into
feat/dialogue-levellerfrom
feat/room-tone-synthesis

Conversation

@lobsterclause

Copy link
Copy Markdown
Contributor

Stack

Stacked on draft #1 (feat/dialogue-leveller), not directly on main. This PR adds only the room-tone work; merge/release is not requested.

Summary

  • Learn noise spectral shape and bounded slow level modulation from explicitly protected word/event gaps.
  • Generate arbitrary-length mono room tone with independently randomized STFT phases and normalized overlap-add rather than repeated loops.
  • Add opendubstage roomtone, reproducible seeds, JSON reports, strict timing validation and input/output collision guards.
  • Add opt-in specrepair --synthesize-tone fallback when no contiguous candidate meets the existing minimum length/context constraints. Existing defaults are unchanged; untouched PCM samples remain exact.
  • Document method, engineering defaults, limitations and experimental roadmap status. No new dependencies or production audio.

Verification

  • Full make verify: 206 tests passed locally (Linux, Python 3.12).
  • 35 focused room-tone cases cover synthetic third-octave spectral agreement within ±1.5 dB, level matching, bounded autocorrelation, seed behavior, silence, timing protection, fallback context, absolute report times, malformed schemas and file-overwrite safety.
  • Independent code review and additional spectral/sample-rate probes found no remaining blocker in inspected scope.
  • git diff --check clean.

Limitations

Experimental mono only; explicit timings/clean selections, no VAD. Slow modulation preserves approximate depth, not the original trajectory or modulation spectrum. Narrow tonal hum and strongly nonstationary sources are not guaranteed. Runtime/memory scale with requested duration. Synthetic checks do not replace listening validation; no listening validation or release claim.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant