Complete AI Training
Sign inGet my AI kit

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

AI agent for audio engineers

Loudness Compliance Multi-Platform Agent

A set of masters, one per platform, each verified against its loudness and peak target

Quality controlComplianceCreatives
See how it worksGet access
Loudness Compliance Multi-Platform Agent: what goes in, what the agent does and what you get

What it does

One master rarely suits every destination. A streaming service wants one integrated loudness, a podcast host another, and a broadcast client a strict range with a true peak ceiling. This agent measures the master's integrated loudness, true peak and loudness range, then compares them with each target platform's published spec that the producer has entered. It suggests limiter and gain settings for each platform, renders a version, measures again and loops until every target passes or a target cannot be met without hurting the mix. It reports which versions pass and which trade-offs it had to make. The engineer approves each master before upload. Edge case: a track that needs 4 dB more loudness for one platform would be crushed, so the agent flags the conflict instead of forcing it.

How it works

Follow the arrows from top to bottom. The orange dashed arrow is the loop: when a check fails, the agent goes back and tries again.

Start and resultWhat it doesA check on its own workWaits for your OKGoes back and retries
Yes, continueYes, continueApprovedNoNo 1 STARTS WHEN Final mix is ready for delivery 2 USES A TOOL Measure integrated loudness, true peak and loudnessrange 3 DOES Compare with each platform target from the spec list 4 DOES Propose gain and limiter settings per platform 5 USES A TOOL Render a version for each platform 6 USES A TOOL Measure each rendered version 7 CHECKS THE RESULT Does every version meet its target loudness and truepeak? If not: Adjust the settings for the failing version andrender it again. Back to step 3. 8 CHECKS THE RESULT Is the loudness range still within 2 dB of theoriginal on every version? If not: Flag the conflict and propose a gentler settingor an exception for that platform. Back to step 3. 9 YOU APPROVE Engineer approves each master before upload 10 RESULT Delivery set with measurement report
Read the steps as a list
  1. Final mix is ready for delivery
  2. Measure integrated loudness, true peak and loudness range
  3. Compare with each platform target from the spec list
  4. Propose gain and limiter settings per platform
  5. Render a version for each platform
  6. Measure each rendered version
  7. Does every version meet its target loudness and true peak?If not: Adjust the settings for the failing version and render it again. Back to step 3.
  8. Is the loudness range still within 2 dB of the original on every version?If not: Flag the conflict and propose a gentler setting or an exception for that platform. Back to step 3.
  9. Engineer approves each master before uploadThe agent waits here for your OK.
  10. Delivery set with measurement report

How it decides

It compares each measurement with its platform target, makes the smallest gain or limiter change that fixes the miss, and flags a conflict when the change would cost more than 2 dB of dynamic range.

  • Keep true peak at or below the platform ceiling, default minus 1 dBTP
  • Prefer gain change before limiting
  • Flag any version that loses more than 2 dB of loudness range
  • Never change the mix itself, only the delivery master

Make it yours

Every agent is a starting point. You choose these settings for your own situation.

  • List of target platforms and their specs
  • True peak ceiling
  • Loudness tolerance (default plus or minus 0.5 LU)
  • Dynamic range loss that triggers a warning
  • File formats for each master

What keeps you in control

It always asks you first

  • Engineer approves each master before it is uploaded or delivered

Hard limits

  • Never upload or deliver files itself
  • Never overwrite the original mix

It stops when

  • Done: All platform versions pass and are approved
  • Stop: A target cannot be met without damaging the mix, so the agent presents the options

Set it up

We guide you through the set-up, step by step

Members get the full set-up guide for this agent. No technical skills needed: you copy, paste and upload.

10 minto set it up in your AI
5 AIsChatGPT, Claude, Copilot, Gemini, Grok
  • One set of instructions to paste into your AI, with the clicks for ChatGPT, Claude, Microsoft 365 Copilot, Gemini and Grok
  • The agent then walks you through connecting your own data, one source at a time
  • A downloadable copy with the flow chart, the rules and the full guide
Get access to this agent

An example run

What happensA mix measures minus 16.8 LUFS with a true peak of minus 0.2 dBTP. The streaming target is minus 14 and the broadcast target is minus 23. Streaming render hits minus 14.2. The broadcast version at minus 23.1 passes, but the podcast version at minus 16 overshoots to a peak of minus 0.4, so the agent lowers the ceiling and re-renders. The engineer approves all three.

More agents for audio engineers

Quality control · Creatives

Audio Dialogue Cleanup Agent

Clean, even dialogue at the target loudness, without damaging speech.

8 steps1 check2 jobs
Quality control · Creatives

Voiceover Pronunciation Repair Agent

Every name and term in the recording matches the pronunciation guide, with replacements that fit the original timing.

9 steps1 check1 job
Quality control · Creatives

Stem Export and Naming Check Agent

A stem package that sums to the mix with correct format and names, ready to upload

9 steps2 checks4 jobs
Document handling · Creatives

Session Archive and Recall Agent

A complete archive that can be reopened later and a safe go-ahead to delete working copies

10 steps2 checks5 jobs