# Big problems with adjusting fader values

**URL:** <https://forum.electra.one/t/big-problems-with-adjusting-fader-values/4126>\
**Category:** Bug reports\
**Tags:** preset\
**Created:** [January 18, 2026, 11:34pm UTC](https://forum.electra.one/t/big-problems-with-adjusting-fader-values/4126 "2026-01-18T23:34:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![klaustrophil](https://avatars.discourse-cdn.com/v4/letter/k/e19adc/32.png) [@klaustrophil](https://forum.electra.one/u/klaustrophil)\
**Post date:** [January 18, 2026, 11:34pm UTC](https://forum.electra.one/t/big-problems-with-adjusting-fader-values/4126/1 "2026-01-18T23:34:48Z")

</div>

There are two problems which makes it difficult to work with my Electra Mini because I need to use it in a live context.

Problem #1: The scaling of the values makes adjustments impossible. I mapped the values of the controls like in the screenshot below

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/electraone/original/2X/3/3c61b1ac7f389592ecf2ac9e650f3701181b5bc4.png)

It only takes something like a 20° turn to go through the whole value range. This makes it extremely fiddly to adjust it. I’d expect around 270 - 360°. Ideally this would be configurable.

I’m aware that the “list” control could kinda replicate this functionality but it takes way more work to enter the values manually and this representation is a bit too small.

Problem #2: The faders in my configuration get stuck at more or less random values and it takes multiple turns in order to “break through” this value. It only seems to happen if I turn the potis rather slow. I mapped the faders like on the screenshot below

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/electraone/original/2X/e/e87cccac7b6c55f3fb89d5eee01581b5948dbcd9.png)

I’m on the latest firmware which was shipped with the Mini.

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/martin/32/145_2.png) [@martin](https://forum.electra.one/u/martin)\
**Post date:** [January 19, 2026, 6:25am UTC](https://forum.electra.one/t/big-problems-with-adjusting-fader-values/4126/2 "2026-01-19T06:25:54Z")

</div>

> [@klaustrophil](#):
>
> It only takes something like a 20° turn to go through the whole value range. This makes it extremely fiddly to adjust it. I’d expect around 270 - 360°. Ideally this would be configurable.

when number of distinct display values go bellow 16, the pot automatically switches to an “encoder” mode. In that mode the steps stay equal and encoder like. When designing this in the very beginning of the project we found it strange when pots with low number of values required dramatically different travel to change from one value to another. Also, it was not in line with other controls such as lists and pads. The Lua function and formatter can be use to completely take control of how this is processed.

> [@klaustrophil](#):
>
> Problem #2: The faders in my configuration get stuck at more or less random values and it takes multiple turns in order to “break through” this value.

I will look at it later today.

---

<div class="post-metadata">

**Author:** ![klaustrophil](https://avatars.discourse-cdn.com/v4/letter/k/e19adc/32.png) [@klaustrophil](https://forum.electra.one/u/klaustrophil)\
**Post date:** [January 19, 2026, 9:13pm UTC](https://forum.electra.one/t/big-problems-with-adjusting-fader-values/4126/3 "2026-01-19T21:13:52Z")

</div>

> [@martin](#):
>
> When designing this in the very beginning of the project we found it strange to when pots with low number of values required dramatically different travel to change from one value to another. Also, it was not in line with other controls such as lists and pads

Sorry, I don’t understand what you mean. The current implementation needs very small physical travel in order to hit the values which is very hard to do. I don’t see the use case where it’s not desirable to have precise control over a small value range. Lists on the other hand take a lot (even a _little_ bit too much for my taste) physical travel to change a value.

> [@martin](#):
>
> The Lua function and formatter can be use to completely take control of how this is processed.

Could you please elaborate on this? In my understanding, the formatter only has an influence on the displayed text so it must be the function. When I create a very basic function like below to keep a value 0 and assign it to a poti, the MIDI value still changes above 0. This prevents me to do value scaling without jumps. What seems to be missing is something like `event.preventDefault()` in JS to prevent further processing down the chain.

```lua
function zero(obj, val)
  local msg = obj:getMessage()
  msg:setValue(0) --will emit 0 after 1 is already emitted
end

```

---

<div class="post-metadata">

**Author:** ![klaustrophil](https://avatars.discourse-cdn.com/v4/letter/k/e19adc/32.png) [@klaustrophil](https://forum.electra.one/u/klaustrophil)\
**Post date:** [January 24, 2026, 9:23pm UTC](https://forum.electra.one/t/big-problems-with-adjusting-fader-values/4126/4 "2026-01-24T21:23:09Z")

</div>

> [@martin](#):
>
> I will look at it later today.

Are you able to reproduce the issue? This is preventing me to use the Mini for performances:/

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/martin/32/145_2.png) [@martin](https://forum.electra.one/u/martin)\
**Post date:** [January 24, 2026, 10:15pm UTC](https://forum.electra.one/t/big-problems-with-adjusting-fader-values/4126/5 "2026-01-24T22:15:47Z")

</div>

yup, I reproduced that. I am now finishing the work on the editor and then I will prepare the first update of the mini firmware.