# Auto pad feature request

**URL:** <https://forum.quantasylum.com/t/auto-pad-feature-request/1818>\
**Category:** QA40x\
**Created:** [April 16, 2025, 11:03pm UTC](https://forum.quantasylum.com/t/auto-pad-feature-request/1818 "2025-04-16T23:03:23Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![skipburrows](https://avatars.discourse-cdn.com/v4/letter/s/8797f3/32.png) [@skipburrows](https://forum.quantasylum.com/u/skipburrows)\
**Post date:** [April 16, 2025, 11:03pm UTC](https://forum.quantasylum.com/t/auto-pad-feature-request/1818/1 "2025-04-16T23:03:23Z")

</div>

Good day all…..  
I was wondering if it’s possible to engage or add the feature that would allow the pad setting to engage when the level is out of range? As you all know the specs get worse as the pad is increased. So it would be wonderful if a feature could be added that would allow for “auto range” as the level increases or decreases. This would be really great as I (and I’m sure many do as well) work in products have very large dynamic ranges and are always needing to constantly change the pad settings really becomes problematic. Ie the console I work on goes out to plus 30 dbu, but nominal level is between +4 dbu and + 18 dbu. So this requires a lot of software juggling to work through a module I build.  
Thanks for any help..  
Cheers  
Skip Burrows

---

<div class="post-metadata">

**Author:** ![matt](https://avatars.discourse-cdn.com/v4/letter/m/a6a055/32.png) [@matt](https://forum.quantasylum.com/u/matt)\
**Post date:** [April 17, 2025, 2:45pm UTC](https://forum.quantasylum.com/t/auto-pad-feature-request/1818/2 "2025-04-17T14:45:06Z")

</div>

Hi @skipburrows, the challenge is that your input level changes based on whether you are wanting an optimal THD or THDN. For example, if your aim is to get the best THDN measurement, on a -2 dBV signal, then you will probably want the 0 dBV setting. If your aim is to get the best THD, then you will probably want a 6 or 12 dBV setting.

Maybe there could be a setting called AutoRange Input Adder similar to the plugins and that is what would be applied. And then after each measurement completes, the full scale input would be updated. And if overload occurs, it switches to +42 dBV full scale input, makes a measurement, and applies.

I think it’s definitely possible.

---

<div class="post-metadata">

**Author:** ![skipburrows](https://avatars.discourse-cdn.com/v4/letter/s/8797f3/32.png) [@skipburrows](https://forum.quantasylum.com/u/skipburrows)\
**Post date:** [April 17, 2025, 3:05pm UTC](https://forum.quantasylum.com/t/auto-pad-feature-request/1818/3 "2025-04-17T15:05:51Z")

</div>

Yes. It seems very possible to do with several “IF-Then” Statements. IE If level is X below Y then decrease the pad. Then the opposite for adding top the pad…

Thanks  
Skip

---

<div class="post-metadata">

**Author:** ![Claudio](https://avatars.discourse-cdn.com/v4/letter/c/7cd45c/32.png) [@Claudio](https://forum.quantasylum.com/u/Claudio)\
**Post date:** [April 17, 2025, 3:14pm UTC](https://forum.quantasylum.com/t/auto-pad-feature-request/1818/4 "2025-04-17T15:14:36Z")

</div>

> [@matt](#):
>
> Maybe there could be a setting called AutoRange Input Adder similar to the plugins and that is what would be applied. And then after each measurement completes, the full scale input would be updated.

I think having an auto range system like some plugins would be a good thing. But it would be important for the user to be able to choose whether to use it or continue with the manual full scale setting