Batch audio QC
Check loudness, peaks, silence, channels, and file properties across a complete delivery.
Sonaudit · Guides
Guides for checking audio deliveries in batches, reviewing technical findings in context, and producing clear QC reports on Mac.
Check loudness, peaks, silence, channels, and file properties across a complete delivery.
Audition candidate clicks, hum, phase, and boundary issues before making a decision.
Turn reviewed results into focused PDF, CSV, or JSON reports for the next stage.
Latest
Extract background music cues, track titles, artists, and exact timecodes from finished videos and audio files on Mac for broadcast and client delivery.
Read articleScan completed video edits and long audio files to identify background tracks, log start times, and build clean music attribution timestamps on macOS.
Read articleUnderstand what audio quality control checks, where listening matters, and how technical preflight differs from editing, mastering, and final acceptance.
Read articleSee why a reconstructed waveform can peak above its stored samples, what dBTP measures, and why true peak cannot replace a loudness reading.
Read articleSeparate Apple's one-decibel headroom recommendation from a true-peak preset, then complete the AAC audition and approval steps a PCM preflight cannot replace.
Read articleRun a repeatable batch audio QC pass, review timed findings, and keep the original files unchanged until the fixes are made in your editor.
Read articleSeparate programme loudness from sampled and reconstructed peaks, and avoid using one number as a substitute for the others.
Read articleUnderstand why drums, edits, and high-frequency material can resemble a defect, then review candidates without turning every transient into a failure.
Read articleChoose a readable review document, a row-based spreadsheet export, or a versioned structured record without sending every internal candidate to the client.
Read articleRead objective threshold failures, content-dependent review candidates, unsupported files, and report status without treating automation as a listening decision.
Read article