preenfm Forum

PreenFM => preenfm2 and preenfm3 => Topic started by: punkdisco on September 22, 2015, 11:05:21 PM

Title: Encoder value jumping by 2 (new build)
Post by: punkdisco on September 22, 2015, 11:05:21 PM
Hi all

Finished my build tonight and surprisingly, it all worked first time!!  :)

The 4 encoders are increasing the values by two.  More precisely, the indents increase by two but if you are careful and get the encoder onto the "dent" you then get the skipped value (so increments by 1).

Is this normal?  Perhaps there is a system setting that allows the indents to increase by 1 rather than 2?

Wonderful synth btw - really looking forward to getting into it..

ta,

Paul
Title: Re: Encoder value jumping by 2 (new build)
Post by: Xavier on September 23, 2015, 09:18:49 AM
Is this normal?  Perhaps there is a system setting that allows the indents to increase by 1 rather than 2?
Paul

Hi Paul,

Seems like you missed the very last line of the build instruction  ;)
http://ixox.fr/preenfm2/build-it/the-pcb-r5/
That redirect to the second entry of the FAQ :
http://ixox.fr/forum/index.php?topic=63377.0
which is :
Code: [Select]
If you need 2 ticks to increase by one the value or if one tick increases by 2 the values, you need to change the encoder drivers.
In the menu (Menu > tools > set > "Rot. enc.") you can chose between 2 encoder drivers: 12 and 24.

The PC/mac editor helps you to understand the underlying structure of the preenfm2.
And donc forget to read the manual (that i still need to update with 2.00 firmware features) :
http://ixox.fr/preenfm2/manual/synth-edit-mode/

Best

Title: Re: Encoder value jumping by 2 (new build)
Post by: punkdisco on September 23, 2015, 08:28:15 PM
Hi Xavier

Yep, this was it  :)  Nice simple Tools menu change and now my knobs increment by 1.

Big thanks; what a wonderful synth!!

Paul
Title: Re: Encoder value jumping by 2 (new build)
Post by: ecstaticsound on November 20, 2015, 05:19:34 PM
I was having the same issue and it was getting really fuckin annoying!

It was quite hard getting to the values I wanted without balancing the encoder's just so.

So glad this was a common issue and the solution was readily apparent.