Analyze Audio Loudness
Measure mean and peak volume, integrated loudness (LUFS), loudness range and true peak, then decide whether to normalize before you edit. Run the preset directly on this page or call the same agent-ready endpoint from your product.
See what the tool changes.
A real example: the after side is the unedited output of a KinoPipe job. Run the live form above to generate the same result from your own media.
Demo footage: public-domain timelapses (Bureau of Land Management, Oregon · NASA SVS). Processed by the same pipeline the API and MCP tools call.
Useful defaults, typed options.
The tool slug stays stable while your agent supplies named media inputs and a narrow set of documented options.
- No encode, analysis only
- EBU R128 integrated loudness
- Pairs with normalize-audio
- 01Decode the audio track
- 02Measure mean and peak levels
- 03Run EBU R128 loudness metering
- 04Return the measurements as JSON
POST /api/v1/tools/analyze-audioKnow the boundaries before you run.
About analyze audio
Which numbers come back?
meanVolumeDb and maxVolumeDb from volumedetect, plus integratedLoudnessLufs, loudnessRangeLu and truePeakDbfs from EBU R128 metering.
How do I decide on normalization?
Streaming platforms target around -14 LUFS. If integratedLoudnessLufs is far from the target, run normalize-audio with the matching preset.