asked Nov 29 '18 at 23:10 by RichardC (113)

If you push the Peak Limiter really hard and then pan a little left or right, the audio breaches the limit and clips the track. Is this a bug? Can anyone else reproduce this?

In Bitwig, a signal which peaks at 0 dBFS panned center will peak at +4.3 dBFS panned fully to one side or the other. The mixer adds or removes gain from each channel (left + right) when panning to make the track seem equally loud, regardless of how it's panned - if it didn't, the track being panned would seem quieter than when it was panned center. This concept is called "pan law". Some DAWs allow you to select which pan law the mixer will use, if any, while in Bitwig it seems to be hard-coded, at least for the moment.

It's also important to note that the device chain is pre-fader in Bitwig. When you apply a peak limiter in the device chain of a channel strip, it limits the signal before the pan knob affects gain for each stereo channel independently, and the fader applies gain to each stereo channel equally.

Since this has nothing to do with the peak limiter itself, you'll get the same result using any limiter, including those mentioned above.


answered Dec 04 '18 at 15:34 by jstrum (56)

Thanks jstrum,

I guess I hadn't really thought of the pan control as being post device chain. But it's obvious if you think about it! Thanks for your detailed answer.

  — (Dec 04 '18 at 16:58) RichardC

Cool! Very informative answer.

  — (Dec 04 '18 at 21:56) djx

Yes. I can reproduce this behavior, but I dont necessarily think its a bug - just a limitation (pun intended). From what I know about how limiter algorithms work they look-ahead and sample the level and decide how to enforce the limit. Lower latency devices (like the peak limiter) sample less often, so there is more chance the will let some peaks through when you push them hard. Why this happens more when panning slightly off center could just be a limitation of a simple limiting algorithm that works on a linked stereo signal. More expensive limiters like those from fabFilter or DMG Audio have many options for dealing better with extreme limiting or for doing it more transparently with less artifacts. But when you want a simple low latency limiter that you can use on every track, the bitwig peak limiter is an excellent choice.


answered Nov 30 '18 at 12:13 by djx (315)

edited Nov 30 '18 at 12:15

Thanks djx for your 'low latency' answer :D

I would hope that a brick wall limiter would not let anything through, even when pushed very hard. The bit I find strange is that this behaviour only happens when you pan more than 4% left or right. I'm inclined to think this is a bug. If it isn't, it would be great to have an explanation from Bitwig.

  — (Nov 30 '18 at 20:08) RichardC

Hi, I've encountered a similar problem with a multitude effects. Compared to ableton anytime I soft clip or limit something, it never pushes beyond 0 db. But in this case, Everything I've thrown in individual tracks as well as the master will push 0 db, sometimes up to +6. Thoughts? I tried to provide a screenshot but I need more Karma I guess.

Experimented with PRO L 2, The Glue with peak limiting turned on, Grid FX soft clipper, Peak Limiter from Bitwig


answered Dec 11 '19 at 23:52 by Alckemy (51)

edited Dec 11 '19 at 23:53

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Nov 29 '18 at 23:10

Seen: 535 times

Last updated: Dec 11 '19 at 23:53