PFL vs AFL on a Mixer: Pre-Fade and After-Fade Listening

TL;DR — PFL, or pre-fade listen, sends a signal from before its fader to a private solo or cue bus, making it useful for checking input level and source quality without raising the audience mix. AFL, or after-fade listen, monitors farther downstream and usually reflects the fader and more of the audible mix path. Exact tap points vary by console, so identify the mode, read the manual, watch the solo indicator, and verify the destination before making decisions.

Table of contents

1. Compare PFL and AFL
2. Understand the solo signal path
3. Use PFL for input inspection
4. Use AFL for output and balance checks
5. Avoid common solo mistakes
6. Build a repeatable cue workflow
7. Document monitoring in a tech rider
8. FAQ

Compare PFL and AFL

PFL usually means pre-fade listen. Pressing PFL routes a copy of a channel to the console's private monitor path from a point before the channel fader. The operator can hear and often meter that signal through headphones, a cue wedge, or control-room monitors while the channel fader remains down.

AFL usually means after-fade listen. Its tap is after the relevant channel, bus, or output fader, so the monitored level follows that fader. AFL is especially useful on aux, group, matrix, and main outputs because it helps the engineer inspect what is leaving that mix path.

PFL and AFL are monitoring functions. They are not the same as selecting a pre-fader or post-fader aux send. An aux tap determines what feeds a mix; a solo tap determines what the engineer privately hears or meters.

Understand the solo signal path

A typical cue path copies the selected signal to a solo bus, then routes that bus to headphones, a console monitor output, a cue wedge, meters, or a combination of these. The normal audience and performer outputs continue independently.

This distinction makes non-destructive solo monitoring valuable in live sound. An engineer can inspect one input while the show continues. However, not every console uses the same labels or tap order. PFL may be before or after input EQ and dynamics. AFL may be post-fader but differ in its relationship to mute, pan, delay, inserts, or output processing.

Follow the console, not the acronym alone

Before relying on a cue reading, answer four questions:

1. Which path is selected: input, aux, group, matrix, main, or physical output?
2. Where is the solo tap relative to gain, EQ, dynamics, mute, pan and fader?
3. Which meter and listening output switch to the solo bus?
4. Is the mode non-destructive PFL/AFL or a destructive solo-in-place function?

Use the console block diagram or manual when the answer matters. A label such as Solo, Cue, Listen, PAFL or SIP can describe different behaviour on different products.

Treat solo level and signal level separately

The solo master or headphone knob normally changes how loudly the operator hears the cue; it does not change the selected channel's actual signal level. Turning up headphones is not the same as adding preamp gain. Likewise, a comfortable cue level does not prove that the signal has adequate headroom.

Use a meter whose reference point you understand. The gain-staging guide explains why nominal level, peaks, fader position and output level must be evaluated at their own points in the path.

Use PFL for input inspection

PFL is a useful first look at an input because the channel can remain out of the main mix while the engineer checks the source.

Set input gain with the right meter point

Ask the performer for a representative show-level signal, select the input's PFL, and watch the console's designated solo meter. Set preamp gain for a healthy nominal level and useful peak headroom according to that console's scale. Then release PFL and place the channel in the mix with the fader.

Do not set gain from a quiet rehearsal whisper and assume it represents the performance. Do not chase a universal meter number across consoles with different reference scales. Pad, digital trim, head-amp sharing and inserted processing can also change which control belongs in the workflow.

Check source quality and patching

PFL can reveal whether the selected input contains the expected source, hum, crackle, RF noise, clipping or excessive spill. It can help separate an input problem from a bus or output problem:

• If PFL is clean but the main mix is distorted, inspect downstream routing, processing and outputs.
• If PFL already contains distortion, inspect the source, DI, microphone, cable, stage box and preamp.
• If PFL is silent, confirm patching, phantom power where required, source state, gain and digital routing.

PFL proves only the path up to its tap point. It does not prove that the channel is assigned, unmuted, sent to the right bus, or reaching the intended connector. Follow the complete live sound signal flow.

Make tonal decisions in context

Solo makes detail easy to hear, but a channel that sounds impressive alone may not work in the full arrangement. Use PFL to identify faults and understand the source. Make final balance, EQ and compression decisions in the appropriate mix and loudspeaker destination.

Use AFL for output and balance checks

AFL helps inspect the result of a fader-controlled path. On a bus or output, it can answer a different question from input PFL: what does this destination currently contain, at approximately what level, after its operational balance?

Listen to a monitor or effects mix

Select AFL on a monitor aux to hear the performers' relative mix rather than one isolated input. Confirm that the correct vocal, instrument, click, talkback and ambience sources are present and that private signals are excluded from unintended destinations.

For an effects return or group, AFL can help verify the processed balance and final path level. Always confirm whether AFL includes that path's EQ, dynamics, mute and output delay on the actual console.

Check a destination without confusing it with the room

Headphones reveal the electrical mix at the selected tap, not the acoustic result from a wedge, IEM earpiece, fill speaker or PA zone. Amplifiers, transmitters, processors, loudspeakers, placement, room acoustics and performer fit remain downstream.

Use AFL to inspect the mix, then verify the real destination safely. For monitor workflows, compare the IEM and wedge paths and establish who owns output level and limiting.

Account for fader and pan

Because AFL follows the fader, a low fader produces a low cue signal. Raising the solo master merely to hear it can make the next selection unexpectedly loud. On stereo paths, AFL may also reflect pan or balance, while PFL may be mono or pre-pan. Check both channels of headphones and meters rather than assuming silence indicates a failed source.

Avoid common solo mistakes

Leaving a solo active

An unnoticed solo can replace the engineer's normal monitor source and main meter view. The audience mix may remain correct while the engineer reacts to the wrong signal. Watch the master solo indicator and clear active selections after each check.

Confusing non-destructive solo with solo in place

Solo in place can mute other channels in the programme mix so the selected path is heard in context through the main buses. That is potentially destructive during a live performance. Never assume a Solo button is private until the console mode is confirmed.

Judging level only by headphones

Headphone sensitivity, cue amplifier level and isolation affect perceived loudness. Use calibrated or understood meters for signal level, and keep monitoring at a safe level. Begin with the solo master down when taking over an unfamiliar console.

Building the wrong monitor mix

Input PFL tells you about one input; it does not reproduce a performer's aux mix. Conversely, AFL on an aux hears the combined bus but may not reveal a pre-fader input problem clearly. Choose the tap that matches the question.

Forgetting shared preamps and digital routing

On systems with shared stage-box head amps, changing gain while checking PFL may affect another console or recording path. Determine whether you control analog gain, gain compensation or digital trim before adjusting it. Coordinate changes with FOH, monitors, broadcast and recording engineers.

Build a repeatable cue workflow

1. Prepare the monitoring destination

Connect and label headphones, cue wedge or control monitors. Start at a conservative listening level. Verify that the solo master, dim and monitor-source controls behave as expected.

2. Confirm the solo mode

Identify PFL, AFL, PAFL, cue or solo-in-place status. Clear any existing selections. Learn whether single, additive or exclusive solo selection is active.

3. State the question

Choose PFL for questions near an input: Is the source present? Is the preamp clipping? Is the cable noisy? Choose AFL for questions near a destination: What is in this monitor mix? What level leaves this bus? Does the return follow its fader?

4. Select one known path

Begin with a labelled source or output. Observe the solo indicator, meters and headphones. Compare the result with the input list and patch sheet rather than guessing from a channel number.

5. Trace only as far as the evidence allows

If a signal exists at PFL, move downstream to assignment, bus, AFL, output patch and physical destination. If it is absent at PFL, move upstream to source, cable, DI, stage box and preamp.

6. Release solo and verify programme monitoring

Clear the selection, confirm the solo warning is off, and make sure normal monitor and meter sources have returned. Listen to the full mix and the actual destination before declaring the path ready.

Document monitoring in a tech rider

A tech rider rarely needs to prescribe ordinary PFL or AFL operation. It should document cue infrastructure when the monitoring destination, private sources, ownership or safety rules affect the show.

In Techrider.live, keep input, mix and output names consistent across the stage plot and input list. Invite the responsible engineer to edit and save the same Rider, inspect history after routing changes, and export a dated PDF for the offline handoff. Describe the required result rather than pretending one manufacturer's solo tap is universal.

Cue and solo checklist

• The active mode is identified as PFL, AFL, PAFL, cue or solo in place.
• The tap point relative to fader, EQ, dynamics, mute and pan is understood.
• Headphone, cue wedge and meter destinations are confirmed.
• Listening level starts conservatively.
• Shared head-amp ownership is clear before gain changes.
• Talkback, click and private sources are excluded from unintended outputs.
• The physical PA, monitor, recording or stream destination is verified separately.
• All solo selections are cleared after the check.

FAQ

What is the difference between PFL and AFL?

PFL normally monitors a signal before its fader, so the fader does not determine the cue level. AFL monitors after the fader and usually represents more of the final channel or bus balance. Both normally feed a private solo bus, but exact processing and mute tap points vary by mixer.

Does PFL affect the main mix?

On a live console's normal non-destructive PFL mode, it does not change the main mix. It changes the operator's cue source and may switch meters. Confirm that the console is not in solo-in-place mode, which can mute other programme channels.

Is PFL before or after EQ?

There is no universal answer. PFL is defined by being before the fader, but a manufacturer may place it before or after EQ, dynamics, mute or other processing. Check the console's block diagram or manual before using PFL to judge a specific processing stage.

What is AFL used for on a mixer?

AFL is commonly used to inspect the post-fader result of an aux, group, matrix, main output, return or channel. It helps check final balance and output level at that tap, while normally leaving the audience mix unchanged.

Why does my mixer sound different in solo?

The solo tap may omit or include different processing, pan, fader, mute and bus summing than the normal listening path. Headphones also bypass the PA, loudspeaker placement and room. Identify the selected mode and tap point, then compare the full mix through its intended destination.

Make every cue answer one routing question

Build a reusable Rider with Techrider.live, give every input and output a stable name, and record only the monitoring constraints another engineer needs. A deliberate PFL-to-AFL trace is faster and safer than changing controls while listening to an unidentified solo path.