Channel Delay vs Output Delay on a Mixer: Timing the Right Path

TL;DR — Channel delay postpones one input before it joins mixes; output delay postpones an entire bus, matrix, or loudspeaker feed. Use channel delay only to align a defined source path, and output delay to coordinate a defined destination with an earlier acoustic or electronic reference. Delay cannot make every seat or frequency perfect. Identify the reference, measure the actual path, change one boundary, and verify every affected destination before saving the setting.

Table of contents

1. Define channel and output delay
2. Choose the correct timing boundary
3. Measure and verify delay
4. Document timing for handoff
5. FAQ

Define channel and output delay

Channel delay, sometimes called input delay, holds one input signal before it continues through the console. It can help align two related electronic or acoustic capture paths, such as a DI and a microphone, when a stable delay difference has been identified. Because that channel may feed FOH, monitors, effects, recording, and broadcast, the insertion point matters.

Output delay holds a complete bus, matrix, or processor output. It is commonly used to coordinate a fill or delay loudspeaker zone with an earlier-arriving reference. Every signal in that output moves together, preserving the internal balance of the mix while changing when the destination arrives.

Delay only moves a signal later. It cannot make a late path arrive earlier. If the chosen reference is already later than the path you control, reconsider the reference, routing, physical placement, or system boundary.

Choose the correct timing boundary

Related input paths

A DI and microphone on the same instrument may arrive at the console at different times because the microphone captures sound after air travel and may include amplifier or processor latency. Compare polarity first, then placement and timing. A small channel delay on the earlier path can improve combination at a defined condition, but the relationship may change when the microphone moves or equipment changes. Review polarity versus phase before treating delay as a universal phase control.

Multiple microphones on one source rarely share one perfect relationship across all frequencies. Physical placement often produces a clearer, more stable result than adding arbitrary delay. Never delay a channel just because two waveform displays do not look identical.

Video, remote, and broadcast paths

Video processors, remote-call systems, plugins, encoders, and network routes can add latency. Choose the intended audience and sync reference, then delay the earlier audio or video path within the correct system. A console channel delay applied for a stream may also affect the room or monitors unless routing provides a separate branch. Build the special destination deliberately rather than compromising every mix.

Front fills and delay loudspeakers

An output feeding a remote loudspeaker zone is normally delayed relative to the chosen main or acoustic reference at a defined listening area. The goal is coherent arrival and a believable source location, not simply converting physical distance into one number. Loudspeaker processing, placement, propagation, environmental conditions, and the measurement position all influence the result. The front fill versus delay speaker guide explains the distinct coverage jobs.

Monitors and IEMs

Extra delay in performer monitoring can harm timing and feel. Do not copy FOH alignment values into wedges or IEM paths. Trace whether a delayed input feeds monitor buses and whether the console can provide an undelayed branch when required. Keep artist monitoring latency as low and predictable as the system permits.

Measure and verify delay

Sound in air travels roughly one metre in about three milliseconds under ordinary conditions, but that estimate is only a planning aid. Temperature and the actual electronic and acoustic paths matter. Use suitable measurement practice for system alignment and confirm by listening throughout the intended coverage area.

1. Name the destination. State whether the work concerns FOH, a monitor, stream, recorder, front fill, or delay zone.
2. Choose the reference. Identify the source or loudspeaker that should establish perceived arrival.
3. Trace latency. Include converters, plugins, sample-rate conversion, networks, processors, and acoustic distance.
4. Verify routing and polarity. Delay cannot correct a wrong patch or reversed polarity.
5. Measure the actual deployed system. Do not rely only on drawing dimensions or a copied preset.
6. Change one delay point. Avoid stacked corrections in the channel, bus, matrix, amplifier, and loudspeaker processor.
7. Listen and remeasure. Check the target area plus transitions into adjacent coverage.
8. Test every affected destination. Confirm that monitors, effects, broadcast, recording, and fills still behave correctly.

Convert time and distance carefully

Some devices display milliseconds, metres, feet, samples, or frames. Those displays may assume a speed of sound or sample rate. Record the authoritative unit and device location. A rounded distance label should not replace the measured delay value.

These figures do not include electronic latency. Do not use them as final alignment proof.

Avoid double delay

Modern systems may expose delay in the input channel, bus, matrix, console output, network endpoint, system processor, amplifier, and powered loudspeaker. Name one owner and one primary adjustment point. Inspect all other stages before adding a value; an inherited preset can otherwise produce a correct-looking total for the wrong reason.

Document timing for handoff

Most artist riders should describe the intended outcome, destination, and ownership rather than prescribe venue-specific loudspeaker settings. A touring system file can carry exact verified values when the physical design is repeatable. Venue-specific timing belongs in the venue or system deployment record.

For a related input pair, document both channels, the delayed path, the insertion point, the verified value, and the condition that makes it valid. Keep the note beside the corresponding input-list and patch-sheet rows.

Common mistakes

• delaying the later path when only added delay is available;
• using channel delay to compensate an entire loudspeaker zone;
• changing system-output timing from FOH without system-owner agreement;
• copying milliseconds from another room or speaker position;
• ignoring latency already present in plugins, networks, or processors;
• aligning one measurement point while making the coverage transition worse;
• sending delayed FOH inputs into performer monitors without checking them;
• recording a number without its device, unit, reference, and recheck trigger.

Delay handoff checklist

• Destination and reference are named.
• Routing, polarity, placement, and existing delay have been checked.
• One person owns each timing boundary.
• The exact device, output, unit, and value are recorded.
• All downstream mixes and recordings have been tested.
• Coverage transitions have been walked and measured where appropriate.
• Recheck triggers and a bypass or fallback state are documented.

FAQ

What is the difference between channel delay and output delay?

Channel delay postpones one input before it reaches downstream mixes. Output delay postpones an entire bus, matrix, or loudspeaker feed. Choose the control that matches the boundary you need to move.

When should you use input delay on a mixer?

Use it when a specific input is consistently earlier than a related reference and delaying that input improves a defined destination without damaging others. Typical cases involve a DI-plus-microphone pair or a dedicated sync path. Verify rather than copying a preset.

How do you set delay for delay speakers?

Choose the main or acoustic reference and target listening area, trace all electronic latency, measure the deployed loudspeakers, adjust the designated output stage, then remeasure and listen through the coverage transition. Distance conversion alone is not sufficient.

Can channel delay fix microphone phase problems?

It can change the timing relationship between related microphones, but it does not correct every frequency-dependent interaction or poor placement. Compare polarity, move microphones where practical, and judge the combined sound in context before adding delay.

Where should delay settings be documented?

Record input-pair timing beside the relevant input rows. Record loudspeaker-zone timing in the system or venue deployment document. Include the reference, device, insertion point, unit, value, owner, verification method, and recheck trigger.

Keep the timing decision traceable

Build and share the current Rider with Techrider.live, connect timing notes to the right inputs and destinations, and invite the responsible engineers to edit the same Rider. Save verified values and inspect history so the next crew knows what was measured, where it lives, and when it must be checked again.