3Deliver

Check the delivery, not just the work

The defect is found at your desk, not at the client’s.

For studios delivering to a broadcaster or a platform

The problem

A failed QC costs a week and a reputation. The three defects that cause it cannot be heard on a play-through: one missing line in the middle of an episode, a loudness one decibel off target, a sync that is right at the start and wrong at the end.

Three checks on the file actually delivered: levels against the broadcast target, the effective presence of every line in the mix, and synchronisation against the timecodes. Nothing is silently corrected: everything is measured, quantified and recorded.

The answer

Levels, on the final file

Integrated loudness, true peak, range, clipping, measured on the deliverable itself, video included, and compared to the chosen target. Every check carries the measured value, not an opinion.

Why show the deviation and not just “failed”? #

Because a verdict cannot be acted on. “−24.4 LUFS, target −23, deviation −1.4” tells you how much to make up; “failed” forces you to measure it again yourself.

And if the file is silent? #

It is reported as silent, not as quiet. The difference matters: a loudness reading on a missing track returns a very low value, which reads as a level problem when in fact there is no sound at all.

Is every line actually there?

The script is compared to the signal, line by line. A line lost during assembly leaves a silent hole at its timecode: the check finds it and takes you there.

How do you tell a hole from a simply quiet mix? #

The threshold is derived from the file itself, not fixed in advance. A deliberately quiet mix is therefore never declared empty, only a genuinely absent line is.

Offset and drift, told apart

The check dates the real onset of every line. A constant offset is fixed in one move; a drift that grows across the programme comes from a frame-rate ratio, and is fixed elsewhere. Two defects, two remedies.

Why is drift so dangerous? #

Because it is zero at the start. You check the first minutes, everything lines up, and the end of the episode is unusable. It is the defect a play-through never finds.

Does Axeho say where the drift comes from? #

When the slope matches a known ratio (24 taken for 23.976, a forgotten resample), the probable cause is named. It is a hypothesis, presented as such, but it is the hour you do not spend looking for it.

A sheet to attach

The three checks run in one action and produce a self-contained sheet, printable to PDF, plus a machine-readable record for archiving. What you send the client states what was verified.

Does Axeho fix what it finds? #

No, and that is deliberate. A check that fixes things by itself can no longer serve as evidence: you would not know what was right and what was patched. Mastering lives beside it, and is triggered by hand.

Specifications

Learning to use it

Step-by-step walkthroughs with screenshots: Check an episode before sending it.