# Limiter on next Firmware update

**URL:** <https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065>\
**Category:** dLive Feature Suggestions\
**Created:** [18 May 2026 13:51 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065 "2026-05-18T13:51:16Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![TrentDugger](https://avatars.discourse-cdn.com/v4/letter/t/898d66/32.png) [@TrentDugger](https://forums.allen-heath.com/u/TrentDugger)\
**Post date:** [18 May 2026 13:51 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065/1 "2026-05-18T13:51:16Z")

</div>

It would be great to have a true peak limiter added on the next firmware update. With all of the great stuff that’s been added over the last few updates, a Limiter within the console would be a huge plus!

Does anybody else think they would benefit from this?

---

<div class="post-metadata">

**Author:** ![duplobaustein](https://avatars.discourse-cdn.com/v4/letter/d/6bbea6/32.png) [@duplobaustein](https://forums.allen-heath.com/u/duplobaustein)\
**Post date:** [18 May 2026 16:04 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065/2 "2026-05-18T16:04:19Z")

</div>

Why would you need a true peak limiter in a live console?

---

<div class="post-metadata">

**Author:** ![J\_McRib](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.allen-heath.com/j_mcrib/32/257_2.png) [@J\_McRib](https://forums.allen-heath.com/u/J_McRib)\
**Post date:** [18 May 2026 16:18 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065/3 "2026-05-18T16:18:35Z")

</div>

Loads of events (namely Houses of Worship) run a broadcast mix from FOH. A true limiter would be useful in that scenario.

---

<div class="post-metadata">

**Author:** ![TrentDugger](https://avatars.discourse-cdn.com/v4/letter/t/898d66/32.png) [@TrentDugger](https://forums.allen-heath.com/u/TrentDugger)\
**Post date:** [18 May 2026 16:23 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065/4 "2026-05-18T16:23:58Z")

</div>

Exactly! I am able to do everything inside the console except for limiting on my broadcast outputs.

---

<div class="post-metadata">

**Author:** ![duplobaustein](https://avatars.discourse-cdn.com/v4/letter/d/6bbea6/32.png) [@duplobaustein](https://forums.allen-heath.com/u/duplobaustein)\
**Post date:** [18 May 2026 17:05 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065/5 "2026-05-18T17:05:30Z")

</div>

The Manual Peak comp has inf ratio and 0,03ms attack. Shouldn’t that do it?

---

<div class="post-metadata">

**Author:** ![J\_McRib](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.allen-heath.com/j_mcrib/32/257_2.png) [@J\_McRib](https://forums.allen-heath.com/u/J_McRib)\
**Post date:** [18 May 2026 17:25 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065/6 "2026-05-18T17:25:17Z")

</div>

You’d think so. I’ve attempted to use it for this purpose before though and the results weren’t super pleasing (to me anyway).

---

<div class="post-metadata">

**Author:** ![hjpa](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.allen-heath.com/hjpa/32/8375_2.png) [@hjpa](https://forums.allen-heath.com/u/hjpa)\
**Post date:** [19 May 2026 11:47 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065/7 "2026-05-19T11:47:34Z")

</div>

Hello,

as far as I know, true peak limiters always require lookahead (which isn’t really feasible in a live setting…😉😉) or have latency. Current plugins need a fair bit of CPU power for this and cause a delay of around 5 ms. That’s likely to be too much for live consoles.  
Do you know of any implementations from other manufacturers?

Kind regards,

HP

---

<div class="post-metadata">

**Author:** ![TrentDugger](https://avatars.discourse-cdn.com/v4/letter/t/898d66/32.png) [@TrentDugger](https://forums.allen-heath.com/u/TrentDugger)\
**Post date:** [19 May 2026 14:17 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065/8 "2026-05-19T14:17:49Z")

</div>

Makes sense for sure. I just like the idea of being able to monitor everything right from the console. I’m doing my limiting now through an external system processor before it hits the stream.

---

<div class="post-metadata">

**Author:** ![duplobaustein](https://avatars.discourse-cdn.com/v4/letter/d/6bbea6/32.png) [@duplobaustein](https://forums.allen-heath.com/u/duplobaustein)\
**Post date:** [19 May 2026 15:57 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065/9 "2026-05-19T15:57:51Z")

</div>

You really need it that hot and limited in a stream situation?

---

<div class="post-metadata">

**Author:** ![J\_McRib](https://sea2.discourse-cdn.com/flex002/user_avatar/forums.allen-heath.com/j_mcrib/32/257_2.png) [@J\_McRib](https://forums.allen-heath.com/u/J_McRib)\
**Post date:** [19 May 2026 17:48 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065/10 "2026-05-19T17:48:21Z")

</div>

“Need” is a funny word to use here. Is it needed for a livestream to be functional? Nah. Is it needed to deliver your message at a level similar to that of other content on the internet? It certainly makes it easier.

---

<div class="post-metadata">

**Author:** ![duplobaustein](https://avatars.discourse-cdn.com/v4/letter/d/6bbea6/32.png) [@duplobaustein](https://forums.allen-heath.com/u/duplobaustein)\
**Post date:** [19 May 2026 21:43 UTC](https://forums.allen-heath.com/t/limiter-on-next-firmware-update/32065/11 "2026-05-19T21:43:49Z")

</div>

Youtube is -14 lufs. EBU is like -23 or something? Idk, should be doable with the current feature set. 🤔

But hey, give us a limiter and/or clipper, I won’t complain, haha. 😜😂
