Also called: Automated QC, AQC, AutoQC or Automatic QC.

Quality control (QC) in media is the inspection of audio and video assets to identify technical, structural or content-related problems. Common issues include invalid formats, incorrect audio loudness, black or frozen frames, audio silence and missing or inconsistent metadata.

Automated quality control (AQC or AutoQC) is the software-based inspection of media files against predefined technical rules. An automated QC engine analyses a file using a configurable template of requirements, limits and tolerances. It then produces a report that helps media teams determine whether the asset is ready for broadcast, streaming, archiving or delivery.

Cloud QC is automated quality control performed using remotely hosted, cloud-based processing resources rather than dedicated QC hardware installed on premises. Cloud QC services can access media in cloud storage, process files on demand and return results to a media management or workflow orchestration platform. This approach is particularly useful when workloads fluctuate or large volumes of content must be checked in parallel.

Detailed definition

How does automated quality control work?

An automated QC workflow begins by applying a QC template to a media file. The template specifies which checks to perform and the acceptable values or tolerances for the intended destination.

The QC engine analyses the file, its encoded audio and video streams, its container or wrapper, and relevant technical metadata. It may return pass, warning or fail results, often with timecodes identifying where individual problems occur.

The results can then trigger further workflow actions. A compliant file might continue automatically to transcoding, packaging or delivery, while a failed file may be stopped, sent for manual review, returned to its supplier or replaced.

What does automated QC check?

The exact tests depend on the media format, destination and configured template. Common checks include:

File and format: Container, codec, resolution, frame rate, aspect ratio, bitrate, duration and file readability.
Video: Black or frozen frames, colour bars, blanking errors, luminance or colour-gamut violations, flashes and other signal anomalies.
Audio: Silence, clipping, excessive peaks, phase problems, incorrect channel count or layout, and programme loudness.
Metadata and structure: Missing or inconsistent identifiers, timecode, track labels, language codes and other required technical metadata.
Specification compliance: Whether measured values fall within the thresholds set by a broadcaster, platform, archive or delivery partner.

Audio loudness tests may use measurements based on standards such as ITU-R BS.1770, but the acceptable target and tolerance must still be defined by the relevant delivery specification.

Automated QC does not necessarily use artificial intelligence. Many important checks are deterministic measurements of signal values, file structures and conformance rules. However, newer tools improve these tests with machine learning for more subjective or content-aware analysis.

Where is automated QC used?

Automated QC can be placed at several points in a media supply chain:

At ingest: Check that incoming masters are readable, complete and compatible with the receiving system.
After transcoding: Confirm that conversion has not introduced errors and that the output matches the selected profile.
Before delivery: Validate a programme against a broadcaster’s, streaming service’s or client’s delivery specification.
During archive migration: Identify corrupt, incomplete or non-conforming material before or after files are moved.
In localization workflows: Check language tracks, channel layouts, subtitles and version-specific technical requirements.

Different destinations can require different QC templates. A file that passes an internal archive profile may still fail a broadcaster or streaming platform’s delivery specification.

Automated QC versus Manual QC

Automated QC is fast, repeatable and suitable for large file volumes, but it cannot determine every aspect of programme quality. A technically compliant file may still contain an incorrect edit, a mistranslated subtitle, poor creative sound mixing or the wrong programme version.

Manual QC uses a trained operator to evaluate technical, editorial and perceptual quality. In many professional workflows, automation identifies measurable errors and directs reviewers to likely problem areas, while people assess context and subjective quality.

Automated QC should also be distinguished from quality assurance (QA). QC examines individual outputs for defects or non-compliance; QA covers the wider processes, controls and practices intended to prevent those defects.