Skip to content
Sign in
/labs / voicelab

VoiceLab

Voice infrastructure Beta
/labs / voicelab
Voice infrastructure Beta

VoiceLab

Is this take usable, and is that note in tune.

Not another voice generator. VoiceLab measures the take you already have: speech QA (noise floor, sibilance, room, pacing) and singing (pitch over time, where it drifted, vibrato and the range you held).

VoiceLab: abstract brand imagery
Live demo · voice QA + singing
VoiceLab · voice QA + singing

VoiceLab QA

Analyse a voice sample for clarity, pacing, pause rhythm, energy in the pauses, clipping risk, and consistency across takes.

Mic capture and analysis stay in your browser. Your audio is never uploaded.

How this is measured

▸ Record a take or drop a file: speech QA above, singing pitch and vibrato below. Signed in? Results land in your Workspace. Your results land in your Workspace.

Also in VoiceLab

Singing: pitch, vibrato and range

The tools above judge a speaking take. This one follows the note. Sing, and see where the pitch drifted, hear that exact stretch back, and get your vibrato and the range you held steadily.

What VoiceLab measures, and why those numbers

VoiceLab is a voice quality analysis tool that runs entirely in your browser. It measures the things you can check before you publish a voice recording: signal-to-noise ratio (how far the voice sits above the noise floor), sibilance energy (the harsh s and t sounds that fatigue listeners), pause energy (what is left in the pauses after speech: noise or reverb, not told apart), speech ratio and speaking rate, long silences, and clipping. Each metric comes back as a number, not a feeling, so two takes can be compared honestly.

That makes it a practical voice debugging tool: when a podcast take sounds off, the numbers say whether the problem is the gain staging (clipping, noise floor), the mic distance (SNR), or the delivery (speaking rate, silences). They do not tell you how well a speech recogniser will cope: in our own test of 1,248 transcriptions, signal-to-noise did not predict recognition errors. They do work for comparing a TTS render with a human recording number by number, and for checking meeting or call recordings before you rely on them.

Everything runs on-device via the WebAudio API: your audio is analyzed locally and never uploaded. When you need the same checks server-side or in an AI agent, the hosted API and MCP server expose this exact analysis as the analyze_voice tool, so a pipeline or agent can check every render with the same numbers you see here.

Singing is a different question, so it has its own instrument below. It follows your pitch over time on a note grid and marks the stretches that stayed more than 25 cents out of tune for longer than a moment, which you can click to hear back. It also reports your vibrato rate and depth, and the range you actually held steady. One honest limit: without the melody it can tell you whether a note sits cleanly on a pitch, not whether it was the right note for the song. That distinction covers most of what singers mean by out of tune: drifting, scooping short, sitting between two notes.

Use cases
Use cases
01

Podcast QA before publish

Catch high energy in the pauses, pacing dips, and inconsistent loudness before the episode goes live.

02

Localization safety net

Flag pronunciation risks and pacing mismatches across language variants before dubbing finalises.

03

E-learning narration consistency

Keep tone, pace, and clarity coherent across 200 recorded modules from three voice actors.

What makes it different
What makes it different

We don’t generate voices. We make the voices you already have (yours, your hosts’, your hired talent’s) measurably better and more consistent.

Also in VoiceLab

  • Pronunciation checker (concept)

    Flag risky words against your target locale. Not built yet.

  • Cleanup preview (concept)

    See what cleanup would do before you commit. Not built yet. VoiceLab measures, it never alters audio.

Roadmap
Roadmap
Now 01
  • QA analyser concept
  • Pacing/filler detection prototype
Next 02
  • Per-episode reports
  • Locale-aware pronunciation flags
  • CLI for batch QA
Later 03
  • Dubbing prep pipeline
  • Studio-grade noise classifier
  • API
Read the system, not the marketing.
Free in the browser · API + MCP at scale

Run VoiceLab from your own code or any AI agent.

The demo above runs free, on your device.The lab above runs free, on your device. The same analysis is a hosted REST API and an MCP server, one key. Loudness is verified against EBU R128 / BS.1770-4. VoiceLab exposes 2 endpoints / 2 MCP tools.

REST · POST

  • /v1/voicelab/qa speech-quality QA
  • /v1/voicelab/segments speech segments

MCP tools · https://audiolab.tools/mcp

  • analyze_voice
  • get_speech_segments

Quick start

curl -X POST https://audiolab.tools/v1/voicelab/qa \
  -H "Authorization: Bearer $AUDIOLAB_KEY" \
  -H "content-type: application/json" \
  -d '{"url":"https://your-audio.wav"}'
Where this leads.