I had an Octatrack Mk1 a while back. I ended up selling it and getting a Mk2 instead, mainly for the improved headroom on the inputs, but also for the added buttons.
I couldn’t help but notice that the encoders are somehow worse on the Mk2. The click feels mushy, and worse yet, their sensitivity makes it harder to delete parameter locks.
Pushing down on an encoder to delete a parameter lock: during the window of time between the moment the parameter lock is deleted and the moment my finger leaves the encoder, a new parameter lock is registered at the value which the encoder was sitting at when I pushed it. I end up having to try three or four times before I’m able to actually delete the parameter lock…
Does anyone have any experience replacing the Mk2 encoders with Mk1 encoders?
2 Likes
Unfortunately I don’t think this is possible. The mk2 encoders are infinite potentiometers. They do something with two wiper blades out of phase with eachother so they’re in quadrature (I’m hastily smashing this out so might not be exactly the term) whereas the mk1s are true/normal encoders. The firmware code for interpreting the turning motion will be different, so they’ll be incompatible unfortunately.
2 Likes
absolutely not possible
@Scooberto with regards your user experience issues - log them, then share your observations, the likelihood is that the issues are less to do with the encoders than you think, i suspect many people will have the same experience as you
wrt the press (accidental turn) issue - i know what you are talking about - it drives me nuts - the turn supersedes the push and there’s often no reason it should monitor turns after pressing - this is a usability issue that can be improved imho
1 Like
I’ll probably send some feedback to Elektron… for an instrument at this price I hope we’ll get some kind of fix
Just chiming in to say I agree about the push/sensitivity a user option in personalize menu would be good.
Related, these endless pots are much more prone to jitter too, which again could probably be taken care of in firmware as @avantronica alluded to in his post.
2 Likes