StringFlux is a transient-aware, multiband granular delay and freeze plugin for stringed instruments. The design goal is to turn one performance into layered texture while preserving playable response.
Design reference for quality, CPU, and audio-thread safety. CPU numbers stay informal until there is a stable build to measure.
| Factor | Goal | Engine behavior |
|---|---|---|
| 1x | Baseline CPU; default monitoring path | No resampler churn; simplest state machine |
| 2x / 4x | Reduce aliasing on nonlinear stages in the wet path | Reconfiguration queued; applied only at safe boundaries |
The engine prioritizes predictable scheduler behavior and stable routing over adding more effect modules early.
Oversampling changes are deferred to safe boundaries to avoid audio-thread instability and state corruption.
Scheduler behavior keeps transient attacks readable and leaves headroom before grain density pegs at the ceiling.
Informal development checks only; no published CPU or latency numbers yet. Benchmarking waits until the core behavior is feature-stable.
Scenario: Oversampling mode change during active playback
Observed behavior: Mode switches queue to the next safe boundary so the audio thread never tears down oversamplers mid-callback.
Engineering value: This keeps behavior deterministic and reduces transition instability risk while tuning the wet-path nonlinear stages.
Scenario: Repeated transitions across 1x, 2x, and 4x modes in dev sessions
Observed behavior: Engine state stays recoverable after mode changes, so dev sessions keep moving without bouncing the plugin instance.
Engineering value: Supports practical iteration speed while validating multiband routing and scheduler behavior.
Current public evidence is intentionally bounded. StringFlux is still in active development, so this section records what has actually been checked without implying release-level compatibility.
Status: In Progress
Public DSP case study and decision records document architecture, constraints, and validation. Core implementation details are kept private for licensing and commercial release planning.
Known limits: No public benchmark or latency claims yet; still validating consistency and host behavior under broader session conditions.
No questions or comments yet. Sign in with GitHub to leave the first one.