**Title:** Mixer Pan should offer “True Pan” (analog-console behavior) — current “Merge & Pan” collapses stereo

[daicehawk1]

**Title:** Mixer Pan should offer “True Pan” (analog-console behavior) — current “Merge & Pan” collapses stereo & breaks insert-driven mixing

Hi Image-Line team and fellow users,

I’m posting a long-standing request that affects real-world mixing habits, especially for anyone who also works on analog consoles or DAWs with conventional pan modes.

## Problem: Mixer “Pan” is effectively *Merge & Pan*, not a console pan pot

On a real mixer (Neve/SSL/etc.) a pan pot behaves like **two complementary gain controls feeding the L and R mix buses**:

* Pan left ⇒ Left gain up, Right gain down
* Hard-left ⇒ **Left = unity**, **Right ≈ off**
* Center ⇒ both sides attenuated by pan law (equal-power, -3 dB / -4.5 dB / etc.)

In FL Studio, the mixer pan behaves like “merge and pan” (cross-mixing), which **collapses stereo differences as you move off-center**. Image-Line’s own docs describe this kind of panning as **mixing L and R together**, making the channels “no longer independent when panned.”

This isn’t just a preference issue; it breaks common mixing workflows and creates wrong muscle memory for anyone moving between FL and “proper” pan implementations.

## Real mixing scenario where this hurts (two stereo beds at the same time)

Example: **two stereo ambience beds playing simultaneously**, both with strong stereo differences:

1. a **street scene** recorded in stereo
2. a **cave/castle dialogue/room tone** recorded in stereo

Goal: create **two simultaneous “scenes”** — one biased to the left and one biased to the right — *but each scene should keep its own stereo/3D atmosphere (“blob”)*.

### What happens with the current Mixer pan

As soon as I pan either bed off-center with the **mixer pan**, the stereo picture collapses toward mono and turns into a **laser-ray narrow image** instead of a wide spatial blob. When both beds are playing, the intended “left blob + right blob” becomes “two narrow rays,” which is the opposite of how cinema / sound-design ambience layering is typically done.

## Why “Stereo separation” can’t fix it (information loss — provable with math)

If the pan stage collapses stereo content toward mono, you lose the independent L and R components. At the extreme (hard-left merge-pan), the operation is essentially:

* (L' = L + R)
* (R' = 0)

Matrix form:

[
\begin{bmatrix}
L'\
R'
\end{bmatrix}
=============

\begin{bmatrix}
1 & 1\
0 & 0
\end{bmatrix}
\begin{bmatrix}
L\
R
\end{bmatrix}
]

That matrix is rank-1 / determinant 0 ⇒ **not invertible** ⇒ it destroys information. Once you’ve reduced stereo to a single sum, the original stereo difference is gone. No later “stereo separation/width” knob can reconstruct the original right-channel ambience; it can only create a *new* “difference” by distributing/phase-manipulating the mono signal. That’s why “pan with mixer knob, then restore width with stereo separation” does not restore the original stereo blob — it can’t.

## Why the common “just use Channel panning” recommendation is not a real solution

A typical reply to this issue is “use the **Channel panning** instead of the **Mixer track pan**.” That doesn’t solve the real mixing problem and, in many cases, it’s actively wrong for professional workflow.

**Reason:** Channel panning happens **before the signal hits the Mixer insert chain**. In other words, it changes the L/R balance **upstream of all insert processing**.

That means any **non-linear / level-dependent processing** on the mixer insert (which is extremely common) will now be driven by a *pre-panned* signal:

* compressors / limiters (threshold interaction changes with pan)
* gates / expanders (keying/threshold becomes position-dependent)
* saturators / clippers / distortion
* transient shapers / envelope followers
* any processor with channel-linked behavior, detector differences, or L/R-dependent detection

So instead of “panning the already-processed ambience blob in the stereo field,” you’re changing the **level feeding the detectors** and changing the behavior of the processing chain based on pan position. This is not how people work on consoles or in most DAWs (unless intentionally doing special effects).

### Quick reproducible example (compressor)

1. Put a **compressor** on the *Mixer insert* for a stereo ambience track.
2. Set it so that at **center**, it’s just touching **~1–2 dB** of gain reduction on peaks (or on the loudest moments).
3. Now pan the track left/right using **Channel panning** (the usual “workaround”).

Result: the amount of gain reduction changes as you pan, because you’re changing the level distribution hitting the compressor’s detector. Small pan moves / automation become unintended dynamics automation. For layered stereo ambiences (two scenes at once), this quickly becomes unworkable.

**In normal mixing practice:** you process the channel/bus (EQ/comp/etc.) and *then* place it in the stereo field with a pan control that does **not** alter how the processors are triggered. If the only way to get “normal pan” is to move panning upstream of inserts, that’s not a workaround — it’s a workflow break.

## Request: Add a Mixer Pan Mode toggle (backward-compatible)

Please add a per-track pan mode:

**Pan Mode**

* **Merge & Pan (legacy / current)** — keep for backward compatibility
* **True Pan (console style)** — no crossfeed; just gains

Where **True Pan** means:

* No L→R or R→L mixing
* Hard-left: Left = unity, Right = mute/off (or very high attenuation)
* Center follows a selectable **pan law** (at minimum: -3 dB equal-power; ideally -3 / -4.5 / -6)

**Backward compatibility plan:**

* Existing projects default to current “Merge & Pan”
* New projects default to “True Pan” (or ask during project creation)
* Optional per-track override so old projects can be migrated deliberately

## Simple verification test

Load a stereo file where L and R are clearly different (different tones or different ambience events).
Move mixer pan slightly left/right and observe:

* stereo difference collapses (content folds), rather than a simple L/R gain tilt

---

I respect Image-Line’s philosophy and the lifetime updates policy — that’s why I’m still here after starting on FL Studio in 2000. But this one has been a pain for over a decade and it affects core mixing technique. A toggle would keep everyone happy: legacy behavior remains, while those of us wanting real console panning can finally work normally.

Thanks for considering.

[mixbynix]

daicehawk1 wrote: ↑Fri Jan 16, 2026 3:13 am **T...

[Parter]

+1 That said, L/R balance is not a "proper" pa...

[daicehawk1]

1. Stereo Enhancer is not a "proper" panning (t...

[Parter]

daicehawk1 wrote: ↑Thu Jan 22, 2026 1:08 pm 1. ...

[Michael Dow]

Yes I want this option in the mixer. New one i...

[Parter]

Michael Dow wrote: ↑Fri Jan 23, 2026 10:50 pm Y...

[Michael Dow]

Parter wrote: ↑Sat Jan 24, 2026 10:32 am Michae...

[Parter]

Michael Dow wrote: ↑Sat Jan 24, 2026 9:03 pm Pa...

[daicehawk1]

Parter wrote: ↑Thu Jan 22, 2026 2:57 pm 1. Pan ...

[Parter]

daicehawk1 wrote: ↑Thu Jan 29, 2026 5:54 am Par...