ADM Master QCPre-Delivery QC · ADM BWF · macOS

The Problem

The problem, stated plainly

A rejected delivery does not come back the day you send it. It comes back a week later, from someone who is not an engineer, with a line that says the file did not meet spec and no indication which part.

By then the session is closed, the client is asking, and you are re-opening a mix you had already signed off.

Most of what gets flagged is measurable before the file ever leaves your room. It just is not measurable by ear.

Checks

What it checks

• Direct Render: whether the master is set to Direct Render, one of the most common reasons an immersive delivery gets bounced
• Loudness against the delivery specification, including the integrated and true-peak numbers
• LFE content, plotted against the specification window, so you see the problem rather than read about it
• Channel and object configuration
• Sample rate, bit depth and file structure
• Metadata completeness, including the fields that silently fail a delivery

Every check prints a result. Where something cannot be determined from the ADM file itself, it says so, rather than passing it quietly.

Honesty

What it does not do

It does not certify your file. No tool can. It checks the published specification and shows its working, so the decision stays yours. Treat the report as a pre-delivery reference, not the sole basis for whether a platform accepts the file.

It does not re-render, re-encode or touch your master. It reads.

The Report

Every run prints a report

A report you can keep, attach to a delivery email, or hand to an assistant.

When something fails, it tells you what to do about it, not just that it happened.

Who It's For

Who it is for

Mixers and mastering engineers delivering immersive masters to major labels, and the assistants who catch the file before it goes. If you have ever had a delivery bounce for a reason nobody could name, this is the tool that names it.