SonauditAudio QC means checking an audio file or delivery against a defined set of technical and editorial expectations before it is handed off. The initials stand for quality control. In practice, the work can range from confirming that every file opens and uses the expected sample rate to listening for an edit click at a reported time.
The important word is defined. A podcast host, audiobook distributor, broadcaster, music service, and private client can all ask for different formats and level limits. Audio QC does not begin with one universal pass button; it begins with the current specification for the delivery.
QC sits between the edit and the handoff
Editing and mastering create the programme. QC examines the resulting files. If a check reveals clipping, the correction belongs in the source session or a suitable editor; the QC record should not silently alter the master it was asked to inspect.
Acceptance is a third step. A clean preflight can show that the enabled checks found no active problem, but only the recipient can accept a delivery. Their ingest system may apply rules that are newer, private, or outside the scope of the QC tool.
- Creation: edit, mix, restore, master, and render the intended audio.
- Quality control: measure the rendered files and review suspicious events.
- Delivery acceptance: apply the recipient's complete checklist and ingest process.
What an audio QC pass normally checks
A technical pass usually starts with file readability and format. Container, codec support, sample rate, bit depth, channel count, duration, and channel layout determine whether the rest of the analysis is meaningful. Level checks can then report sample peak, true peak, integrated loudness, short-term or momentary loudness, and loudness range where the workflow needs them.
Content checks look for conditions such as sustained clipping, long silence, abrupt boundaries, possible clicks, hum, DC offset, channel imbalance, or phase concerns. A batch adds another layer: inconsistent formats, duplicate content, naming conflicts, missing sequence numbers, or one file whose loudness differs from the rest of the delivery.
Some results are measurements; others are questions
A measured true peak above a selected ceiling can be compared directly with that rule. A file that cannot be decoded is also an objective limitation, although it should be labelled unsupported rather than passed or failed as if the analysis had completed.
Possible clicks, hum, negative stereo correlation, and internal silence are different. Music and speech can naturally resemble those patterns. A detector can identify a useful time to inspect, but a reviewer still has to hear the event in context and decide whether it is unintended. Good QC separates those candidates from confirmed failures instead of turning every alert red.
A repeatable audio QC workflow
Keep the delivery together, choose the specification that applies, and scan the complete batch. Read the batch summary before opening individual files so that an outlier does not disappear among otherwise consistent results. Then work through failures, unsupported files, and listening candidates in that order.
Audition timed findings, record whether each one is confirmed, ignored, or still pending, and make corrections outside the QC app. Replace or rerender the source files, rescan them, and compare the new result with the earlier record. Export a report only when its audience and purpose are clear.
- Use the recipient's current specification instead of relying on a preset name alone.
- Do not treat an unsupported file as evidence that it is clean.
- Keep unresolved listening candidates in an internal report until someone reviews them.
- Rescan any file that changes after the first report.
What Sonaudit covers and where it stops
Sonaudit is a local macOS batch preflight tool. It reads selected files and folders, presents measurements and timed candidates, keeps review decisions in saved projects, and can export PDF, CSV, or JSON reports. The source audio remains unchanged.
It does not repair audio, replace a DAW, certify compliance, or guarantee that a distributor will accept a file. It is most useful when a person needs a consistent first pass and an auditable review queue. For a creative mix decision, forensic restoration, or a proprietary ingest failure, use the source editor or the recipient's own validation tools as well.