WaveLens the toolkit answers one question: does this file still sound the same, and if not, how? These services go a step further into objective audio testing — for algorithms and products where the right test isn't just “run the six checks,” but something built for what you're actually shipping.
Custom test packages
For teams building a codec, an encoder, or an audio post-processing algorithm — noise reduction, dynamics processing, upmixing/downmixing, anything that transforms audio and needs to be verified, not just listened to.
We design a test package around what your specific algorithm actually needs to prove: reference and stimulus material chosen for the failure modes that matter for that algorithm (not generic tones), pass/fail tolerances calibrated to what “correct” means for your use case, and a repeatable suite your team can run against every future build — not a one-time audit.
- Test signal design targeted at your algorithm's real failure modes, not off-the-shelf material
- Tolerance and pass-criteria definition specific to what you're building
- A regression suite structured to run the same way every time, so results are comparable release to release
- Documentation your team can own and re-run without us
This is early — reach out and tell us what you're building, and we'll figure out together whether a custom package makes sense for it.
Technical consultation
For teams with an existing audio product who need help figuring out how to test it properly — where the gap isn't a missing tool, it's a testing strategy.
- Reviewing what you're currently doing and finding the blind spots
- Helping define what “correct” even means for your product
- Advising on how to structure a QA process that scales past manual listening
Tell us what you're building
Both of these are new and evolving — get in touch with what you're working on, and we'll figure out from there whether it's a fit.