QC Workflows

Different situations call for different approaches. This page outlines common QC workflows to help you get to a confident decision quickly — whether you have five minutes or an hour.

Quick QC pass

When to use: You need a fast sanity check, or you're doing an initial pass before a deeper review.

What you're looking for: Obvious problems — clipping, missing channels, broken automation, or glaring spatial issues.

1. Load the file and let import complete (waveforms should appear).
2. Skim the densest section — scrub to where the mix is busiest and play for 30 seconds. Watch the meters for clipping and the 3D scene for object motion.
3. Check the 3D view — do objects move as expected? Any stuck or jumping objects?
4. Scan the meters — are all expected channels active? Any unexpected peaks?
5. Switch to Stereo — play the same section. Do essential elements remain audible, or does the fold-down mask key parts of the mix?

If everything looks reasonable, you've got a baseline. If not, you know where to dig deeper.

TIP

For a quick confidence check, inspect three moments: the opening, the densest section, and the final minute. These often surface the most common problems.

Object sanity check

When to use: You want to verify that specific objects are positioned and automated correctly.

What you're looking for: Correct positioning, smooth automation, no unexpected jumps or dropouts.

1. Open the Objects tab in the sidebar and locate the objects you want to check.
2. Select an object — click to highlight it with a white ring in the 3D view.
3. Solo the object — click the S button to hear it in isolation. A yellow ring appears.
4. Scrub through the timeline — move slowly through sections with known automation. Watch the 3D view and listen for smooth transitions.
5. Check multiple objects — repeat for other key objects. Use Shift+Click to select a range, or Command+Click to add individual objects to your selection.

Pay attention to:

• Objects that should move but stay fixed
• Sudden jumps that don't match the musical content
• Height moves that feel exaggerated or absent
• Objects that go silent when they should be active

Binaural translation check

When to use: You need to verify that the spatial intent translates well to headphones.

What you're looking for: Clear front/back separation, audible height cues, and a stable spatial image.

1. Switch to Binaural mode in the Settings tab.
2. Put on headphones — ideally the same type your audience will use.
3. Enable head tracking if available (AirPods or camera). This keeps the soundstage stable as you move.
4. Play through key sections — focus on moments with front/back movement, height changes, or wide panning.
5. Toggle head tracking off — compare with and without. Does the spatial picture hold up either way?

Things to listen for:

• Can you clearly tell when something is in front vs. behind?
• Do height elements feel elevated, or do they collapse to ear level?
• Is the center image stable and focused?
• Does panning movement feel smooth or jumpy?

Full delivery review

When to use: You're signing off on a deliverable and need thorough confidence.

What you're looking for: Complete validation across all monitoring modes, with documented findings.

1. Start with the Quick QC pass to catch obvious issues.
2. Run through in 7.1.4 mode (or your speaker setup):
   • Verify beds map to the correct speakers
   • Confirm object panning matches spatial intent
   • Check LFE content is present where expected and absent where it shouldn't be
3. Switch to Binaural mode and repeat the key sections:
   • Validate front/back separation
   • Confirm height cues translate
   • Test with and without head tracking
4. Switch to Stereo mode for fold-down validation:
   • Confirm essential elements remain audible
   • Check for phase issues or masking
   • Verify the balance feels intentional
5. Capture notes — write down any issues with timecodes and object names.

For a structured checklist to work through, see Delivery Checklist.

Comparing monitoring modes

When to use: You want to understand how the mix translates across different playback environments.

What you're looking for: Consistency of intent — does the spatial picture hold up, or does translation reveal problems?

1. Pick a reference section — choose a moment that represents the mix well (good density, spatial activity, representative content).
2. Play in 7.1.4 mode — note the object positions, balance, and spatial spread.
3. Without moving the playhead, switch to Binaural mode — listen for the same section. Does the spatial intent translate? What's gained or lost?
4. Switch to Stereo mode — same section. Is the balance still there? Are key elements masked?
5. Repeat for other sections — especially transitions, quiet moments, and the densest parts.

This workflow helps you understand how robust the mix is across playback environments. Issues that appear in only one mode may indicate problems worth addressing.

Investigating a specific issue

When to use: Someone reported a problem at a specific timecode, or you noticed something you want to understand better.

What you're looking for: The root cause — is it the ADM, the content, or a rendering artifact?

1. Navigate to the timecode — scrub or enter the time directly.
2. Identify the suspect — which object or bed seems involved? Select it in the sidebar.
3. Solo the element — listen to it in isolation. Is the problem in the source content?
4. Check the 3D view — is the position correct? Does automation look smooth or jumpy?
5. Switch monitoring modes — does the issue appear in all modes, or only some?
6. Use the Performance HUD (⌘⌥D) if you suspect a rendering issue — look for underruns or faults.

Once you've isolated the problem, capture the timecode, object name, and a description. This makes it easy for the mix team to reproduce and fix.

Document your findings

When you find issues, write down the timecode and object/bed name. This helps the mix team reproduce the problem quickly and shows them exactly where to look.