# Encoder resolution

**URL:** <https://forum.electra.one/t/encoder-resolution/643>\
**Category:** Ideas / Feature requests\
**Created:** [May 3, 2021, 9:40pm UTC](https://forum.electra.one/t/encoder-resolution/643 "2021-05-03T21:40:35Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![joris.roling](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/joris.roling/32/375_2.png) [@joris.roling](https://forum.electra.one/u/joris.roling)\
**Post date:** [May 3, 2021, 9:40pm UTC](https://forum.electra.one/t/encoder-resolution/643/1 "2021-05-03T21:40:35Z")

</div>

Hi @martin,

Would it be possible, for certain controls, to _lower_ the resolution, meaning instead of having (say) a fader move from **min** to **max** in one rotation of the encoder, allow for more precise control by needing 2 (or 4) rotations to get it from **min** to **max**.

My use case is a Program Change fader, where I want to set it to an exact number. It currently is rather _fiddley_ to get to the next value: I would love to travel a bit more before the next (integer) value is reached.

So some parameter like **speed** (fast/slow) or something would help me here.

Hope I did explain my Idea / Feature right (if not please say so).

---

<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:** [May 4, 2021, 5:32am UTC](https://forum.electra.one/t/encoder-resolution/643/2 "2021-05-04T05:32:05Z")

</div>

Technically yes. electra calculates the step size based on number of distict values and the speed of rotation. Below 32 values (I think) it goes to the encoder mode where fixed travel is required to generate one step. Maybe forcing the encoder mode would do the job?

---

<div class="post-metadata">

**Author:** ![joris.roling](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/joris.roling/32/375_2.png) [@joris.roling](https://forum.electra.one/u/joris.roling)\
**Post date:** [May 4, 2021, 6:29am UTC](https://forum.electra.one/t/encoder-resolution/643/3 "2021-05-04T06:29:54Z")

</div>

Maybe indeed, would that be possible as an option? Maybe JSON only, to start off with?

---

<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:** [May 4, 2021, 6:44am UTC](https://forum.electra.one/t/encoder-resolution/643/4 "2021-05-04T06:44:44Z")

</div>

yes, I see it could be an optional attribute in the in preset json.

---

<div class="post-metadata">

**Author:** ![joris.roling](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/joris.roling/32/375_2.png) [@joris.roling](https://forum.electra.one/u/joris.roling)\
**Post date:** [May 4, 2021, 12:49pm UTC](https://forum.electra.one/t/encoder-resolution/643/5 "2021-05-04T12:49:10Z")

</div>

Cool! And hopefully in the **Instrument Files** as well?

---

<div class="post-metadata">

**Author:** ![kirkwoodwest](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/kirkwoodwest/32/14_2.png) [@kirkwoodwest](https://forum.electra.one/u/kirkwoodwest)\
**Post date:** [February 13, 2022, 7:19pm UTC](https://forum.electra.one/t/encoder-resolution/643/6 "2022-02-13T19:19:23Z")

</div>

yes, i am also wanting some sort of encoder speed. i’m wanting to try to get these encoders to be 270 degrees for full rotation 1 - 127 values. should be enough resolution there with the pots?

---

<div class="post-metadata">

**Author:** ![akira](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/akira/32/799_2.png) [@akira](https://forum.electra.one/u/akira)\
**Post date:** [February 18, 2022, 5:22pm UTC](https://forum.electra.one/t/encoder-resolution/643/7 "2022-02-18T17:22:03Z")

</div>

I’m away from my Electras to provide an example, but you should be able to use a Lua function to scale values as you see fit. I agree it’s a good idea for the firmware itself to provide the means to deal with this, but if you’re in any way blocked you can give Lua a try.
