I build software when a question is easier to understand by exploring it. Some tools are focused utilities. Others are more complete measurement and design environments. They are meant to be useful first — and to make the assumptions behind the result easier to see.
Larger environments built around recurring acoustic questions and real workflows.
Dual-microphone response matching & calibration.
Compare a microphone against a reference, capture the response difference, derive the required correction, fit parametric EQ, and export calibration information.
Interactive critical-listening room modelling and treatment placement.
Explore room geometry, listener and monitor placement, first reflections, modal context, octave-band decay estimates, and treatment in one visual environment.
Quick to use, explicit about the math, and designed to help explain the result rather than just return a number.
Source and microphone-array recording-space designer for exploring placement before committing to a setup. Compare geometry, path length, off-axis angle, arrival time, relative phase, and stereo perspective in one visual workspace.
1D / 2D quadratic-residue diffuser construction designer with fabrication controls and a live geometry preview that keeps the build dimensions visible.
Acoustic absorber system designer for building and comparing layered assemblies. Explore materials, air gaps, construction depth, and frequency-dependent absorption behavior in one working model.
Convert parametric-EQ Q to octave bandwidth and back, with optional cutoff frequencies.
Solve circular-arc barrel-diffuser geometry from common known dimensions for layout and fabrication.
Calculate wavelength from frequency — and frequency from wavelength — as a quick acoustics reference.
The best tools make technical ideas easier to explore, understand, and apply.
A calculator can answer a defined question. A real room, product, or measurement problem usually contains assumptions the calculator cannot see. Good software should make those boundaries easier to recognize and help the user ask the next useful question.
Useful first. Clear about assumptions. Built from real practice.
If the problem comes up often enough, it may be worth building the right instrument for it.
Tell me what you're working on, what matters about it, and where you are in the process. A short note is enough to start.
