Digitone 2 FUNC Button and Encoder Issues

Elektron Gear Digitone/Digitone Keys
1

Anyone else running into weird FUNC and encoder behavior on the Digitone 2?

  1. Pressing FUNC sometimes opens the Preset Pool even when I’m not touching the Level encoder.
  2. When I’m adjusting LFO settings or Macros, the encoders randomly reset or jump back to the top value.

It’s happening often enough to break the flow and I can’t tell if this is a firmware bug or a hardware issue. Already tried rebooting and testing across different projects but it keeps happening.

If you’ve had this happen or figured out the cause, would love to hear your experience.

2

My LFOs behave funnily. The DT2 has no issues but the DN2 jumps around on the LFO menu. Whilst I’m scrolling through target destinations it often clicks itself off the menu.
I get some lag on changing LFO speed and multiplier whilst a pattern is playing. None of this is too invasive but I do notice it

3

Yeah thats exactly what i have but a little more extreme sometimes. There are moments where choosing values become a 5 min challenge :cold_sweat:

4

This happens on my unit as well. Sometimes. The destination list thing.

1 Like
5

I’ve had the FUNC button issue and one of my encoders was twitchy. I used test mode to double check encoder behaviour and it was indeed problematic. I contacted Elektron’s customer service and got it fixed.

Funny thing is, I dropped it to their warehouse cause I live nearby and by the time I got home I’ve had a mail from them that it’s fixed and ready for pickup.

6

Huh ok let me try and reach them about this. I tried test mode and indeed some of the encoders move/twitch a bit after i touch it around.

Im hoping its something that can be repaired locally. Im from the Philippines and getting it shipped is quite a hassle.

7

Things like this have been happening since the DT first came out, its down to encoders being too sensitive imo, it happened a lot whilst microtiming ime as every encoder is wired to fast scan and it only takes one of them hovering around the boundary of triggering to interupt your own input You can often remedy the problem by giving the encoders in question a turn.