About
Component-modeled, not preset-packed
Who is CarbonDSP?
CarbonDSP is a small team based in Nashua, New Hampshire — two developers, plus a handful of UI/UX designers, vocalists and sound designers. Everything is built in-house and end to end: the DSP model, the interface, and the release that ships it.
What does “component-level-modeled” mean?
Most audio software approximates a sound with a single algorithm tuned to feel roughly right. CarbonDSP plugins instead model the signal path stage by stage — the way it actually moves through real circuitry, not a shortcut around it. A tube preamp, for example, isn’t one saturation curve: it’s a gain stage, a bias point that shifts under drive, interstage coupling, and output-transformer coloration, each modeled and then chained together. The result tracks how the real thing behaves across its whole range, not just at one setting that was tuned to sound good in a demo.
How is a release actually verified?
Every plugin goes through the same gate before it’s published: an offline render-smoke pass exercises the DSP directly, a headless UI snapshot catches visual regressions, and pluginval runs at its strictest validation level (10) against the real build. Once that pipeline is verified, we run each plug-in and standalone version on a variety of machine builds to verify that it is stable and as bug-free as possible.
What’s next?
More plugins are in active development and will join the catalog as they clear the same verification gate every existing release went through — no shortcuts for being newer.
Questions?
Check the FAQ first, or contact support directly.