Hi,
Don’t know if this has been talked before …
This morning i installed FW 1.1.20 on my Sub 37 and while tweaking some sound i noticed that 0 and 127 values were reached before respectively low and high knob position (verified with MIDI Monitor).
This behavior appears on ALL knobs 
Please see an example for low position on the picture bellow (hi position is the same).
I performed a pot calibration twice but it doesn’t change anything !
Does anybody noticed this ?
Hi,
I notice this Some weeks ago. We where talking about it in a thread. The problem was about oscillator wave1/wave2. that was nearly the same problem.
I did also calibration just for this 2 pots. but it did not help.
And yes Now I notice that All the pots have the same problem.
Maybe the calibration file what I got from Moog is not OK.
I Just Look at midi Monitor and yes you are right.
All the knobs start late…
I also notice that you can see the knob reaction in the editor.Moving late
Lets see…
Regards Luloop
My guess would be that since the knobs have a much higher resolution using two bytes, the MSB contains the 0 - 127 value as you see it in as MIDI CC, but each of those 128 steps has another 128 within. That means in the range where the knob is 0, there were already 128 position values transmitted using the LSB. But those are ignored for normal MIDI CC messages.
But then again, I might be talking outta my behind… 
hi,
It doesn’t matter if the knobs have higher resolution or whatever. When I turn on a knob it has to function well and not that there is a gaps in between. (2 gaps…from 19 o’clock to nearly 20 o’clock and from 5 o’clock to 4 o’clock).
Has somebody else this issue ???
Regards Luloop
pretty sure this is normal for the Sub37 hardware, the mechanical travel of the knobs is less than the electrical travel. The conductive material causing value change when turning the pot, has a physical deadband at the ends. It’s always been this way. Not a function of firmware or calibrations.
Hi Amos.
Good to know.. I was feeling funny about this…
Have a nice weekend and take care.
Warm regards Luloop
Hi,
Just tested now and it’s the same behavior with the Minitaur’s knobs !
Never noticed that before but if it wasn’t problematic before, it won’t be now 
Thanks for the clarification Amos
Is this related to the phenomena of moving the hardware knob to a 9 o’clock position, and seeing the editor knob at 8:30 or lower? Likewise, with 3:00 on the hardware giving a 3:30 or 4:00 position in the editor.
Yes it’s the same thing. there isn’t a precise mapping between the rotational angle of the hardware knobs and the software-UI knobs, or rather there is a different mapping, with respect to the same parameter value indicated on each type of knob. 