When I updated my A4 to the latest firmware, I observed, that the most left data entry knob in the lower line (data entry knob “F”) behaves weirdly.
It looks like the acceleration of the knob is not kept correctly. So when selecting the filter 2 frequency I got only two options: going very slowly through the frequencies by turning the knob quite fast or using the stepping option with the knob pressed.
So what I do now is to jump to the preferrend frequency range and then use the fine tune, which takes quite long.
The knob definitely behaves differently to all the other knobs.
So the question is, if this is just a (known) error within the OS or do the A4 has a faulty knob?
have you already tried to reload the OS, or do a “factory reset”?
if it doesnt respond to either of those, it could be an issue with the knob or something like that… who knows tho, it may not be an actual hardware issue, but rather just something that can be fixed by elektron techs but not end users (since they have more knowledge and tools available)
I doubt it would be an OS thing, likely just a coincidence, but what do I know !
Anyway, I believe there is a mode in the Test Menu whereby if you twist the encoders you chase the sequencer lights, I have no idea if this is intended to be a visual gauge of the encoder’s performance, but it won’t do any harm to enter the test mode and try this encoder against the others there
Also try ending the MIDI output in performance mode to a MIDI monitor prog or other destination that you can use to test the feel of the encoder output relative to its neighbours
1 Like
could be less of a coincidence and more of a hardware issue that only appeared due to firmware changes… thats pretty common
maybe so, but I can’t see why it would be particular to only one of the encoders, but yeah, I guess a tweak to an algorithm could highlight a previously largely masked issue … though I doubt encoder feel has been touched
either way support will guide the OP towards resolution
1 Like
malfunctioning flash rom chips can do very odd things… and if that was the case it may have other issues the OP hasnt discovered yet
1 Like
that’s a good insight, hadn’t thought along those lines 
Sorry guys, I was a bit off last days…
Had a look, but didn’t found a “Test Menu”.
Looks, like I’m adapting slowly to the encoder behaviour. If it is turned slowly, the values increment in fine steps. If it’s turned with “medium” speed, the stepping is increased, as it is intended to do. If the encoder is turned fast, the encoder stepping is very fine again.
