TOP 5 QC Errors

Written By Oliver Dacosta-Woodall

Nothing kills the vibe like this message landing in your inbox 😭

“Your file has failed QC. Please re-deliver.” 

Whether you’re submitting to a broadcaster, platform, or client, technical quality control (QC) is the final gate your content needs to pass before it gets aired, uploaded or signed off. And if it fails, it’s not just annoying—it can be costly.

Here are the 7 most common QC issues that delay deliveries (based on real-world data) — and how to avoid them.

1. 🧠 PSE Flashing Failures (The “Harding Test”)

The problem: Your content includes flashes, patterns or transitions that may trigger photosensitive epilepsy (PSE) in viewers.

How it’s flagged: Your file fails the PSE Test — a legal requirement for broadcast in the UK and many other regions.

Typical causes:

  • Flashbulbs or strobe effects

  • Fast-paced editing or glitch transitions

  • Animated graphics with intense contrast

How to avoid it:

  • Reduce high-contrast flashes and flicker in post

  • Avoid copy-pasting effects without checking compliance

  • Run a PSE check before delivery using QC Kitchen

✅ QC Kitchen can run a PSE test, so you know in minutes if your content is safe to broadcast.

2. 🎚 Loudness Issues

The problem: Your audio is too loud or too quiet and doesn’t comply with the EBU R128 or Online loudness standard.

How it’s flagged: Audio meters exceed target LUFS levels, especially during dynamic sections.

Typical causes:

  • Manual mixing without referencing a loudness meter

  • Dialogue/VO inconsistencies

  • “Hot” exports from music or promo videos

How to avoid it:

  • Use a loudness meter plugin when mixing

  • Keep final mix at -23 LUFS ±0.5 (for EBU R128) and -16 LUFS (the web standard)

  • Run an automated loudness scan at QC Kitchen before delivery

✅ QC Kitchen measures and validates audio levels across your file — including momentary and integrated loudness.

3. ⚠️ Illegal Luma or RGB Levels

The problem: Your video includes brightness or colour values that are “out of spec” for broadcast — also called “illegal levels”.

How it’s flagged:

  • Luma below 0% or above 100%

  • RGB values clipping or bleeding into each other

Typical causes:

  • Grades pushed too far in Resolve or Premiere

  • Improper import or export settings

  • Overlay graphics not adjusted for safe range

How to avoid it:

  • Use broadcast-safe filters or scopes during grading

  • Export using legal range settings (16–235 luma)

  • Check levels using QC Kitchen before delivery using scopes

✅ QC Kitchen flags out-of-range luma/chroma values and shows frame-accurate problem areas.

4. ❌ Dead Pixels

The problem: A stuck or missing sensor pixel appears in your final output — often a small white, red or black dot that doesn’t move.

How it’s flagged: Manual review or pixel scan tools catch the artefact.

Typical causes:

  • Sensor fault on a camera body

  • Poorly handled rushes or dailies

  • Missed in post due to small screen size or proxy workflows

How to avoid it:

  • QC your footage during dailies using dead pixel detection

  • Check final exports at 100% zoom

  • Automate your pixel scan with QC Kitchen

✅ QC Kitchen dead pixel detection is ideal for DITs and editors working with new or rental kit.

5. ⬛️ Blanking Errors and Black Frames

The problem: Your file has black lines that appear at the edge of frame, these can be as little as 1 pixel wide or Black Frames which are whole frames of black as short as 1 frame  

How it’s flagged: Manual or automated checks at the broadcaster reject the file due to blanking occurring on either the top or bottom, left or right side and Black Frame detection. 

Typical causes:

  • When resizing shots moving the clip too far so the edge is visible in the preview window

  • Having a gap on your timeline between clips

  • Exported without checking your timeline for black frames

How to avoid it:

  • QC your timeline using an eagle eye to spot blanking errors

  • Use QC Kitchen to show you exactly where these blanking errors and black frames are

✅ QC Kitchen checks for blanking issues and black frames and holes, showing you what frames need fixing

The Fix?

Automate Your QC Before You Deliver.

We built QC Kitchen so media professionals like you could run a full broadcast-standard QC scan in minutes — without sending files off to an external facility or waiting hours and hours.

Whether you're a:

  • Freelance editor delivering a TV ad

  • Post house finishing a docuseries

  • DIT checking dailies for sensor issues
     

PixelPantry helps you catch the problems before your client or the broadcaster does ✅

🎯 Want to QC your file before it causes problems?
 Try QC Kitchen free — and deliver with confidence.

👉 Run a Scan with QC Kitchen

QC Kitchen
Oliver Dacosta-Woodall
Next

AS11 Delivery Explained