Haven’t been near my digitone in a while so I haven’t checked out 1.32 for myself yet, but since @Kaffekopp is also reporting it’s still there it seems that they have either forgotten about it or haven’t gotten around to it yet. I also don’t see it in the change log. Elektron has confirmed it to be a bug quite a few months ago.
There was another pretty nasty bug in 1.31 that Elektron confirmed, that I also don’t see in the change log. I won’t be near my DN next couple of days so perhaps someone could confirm it’s still there? It’s really easy to reproduce:
Bug: In the LOAD PROJECT menu, performing any of the copy/clear/past operation through the [FUNC] + [REC]/[PLAY]/[STOP], performs it on the project placed 1 position above the cursor instead of at the cursor position.
This is not the case in the SAVE PROJECT AS menu or the MANAGE PROJECTS menu. Luckily the popup confirmation dialog window displays the name of the project that you perform the operation on and not the project-name corresponding to the project that is at the cursor position. Still nasty and if it’s still there, it’s obvious low hanging fruit ^*^
There’s too much new odd behavior that didn’t exist before in this new update as it pertains to voices being unpredictable in ways that used to be air tight when it came to repeating the intended tone and timbre.
I don’t understand why so much has changed in this regard when it seems a majority of the changes in this update were UI-based with the exception of the filter’s delay.
This is why I don’t like ‘updates’ in general…they tend to just introduce new bugs or break once-working elements of the software/hardware. Did anyone in Elektron even test this release? Did an early beta of this update accidentally get labeled as the release candidate and there’s actually a stable and working one that exists misplaced in the wrong folder on one of the software engineer’s hard drives? I refuse to believe this update went out the door in this state on purpose.
I confirm that I also see this issue of lagging knobs no matter the page I’m on and not only the D one but all of them. makes it almost impossible to tweak parameters live.
I remember Ess saying that program change is problematic since it has to come in advance (IIRC). I guess it comes too late then although it must be nearly instant. But actually it could come in advance in connection with pattern switching (FUNC+PTN key) since you are switching or cuing up a pattern before it’s actually happening. So the PC could be send a little before.
Well, in theory I would agree … except it works with no CH.Len set.
The problem occurs only if you define one.
The support literally told me it was a known bug and was one of the highest priority (well, I have the feeling they say this to most of the problems though). Let’s see if they actually do something about it, but it seems to be a recurring problem for years now.
There is a known bug that can cause patterns to change too late when the receiving device is in PER TRACK scale mode and the master length is higher than 16. This issue has the highest priority to be fixed, but it is unfortunately complex and time consuming. We hope that a fix can be ready soon.
I get a glitch where the LFO destination list meny goes on and off, without touching the corresponding encoder.
I have a hard time reproducing it consistently, because it works fine when I’ve just started the unit, and seems to appear after a while.
Also, it seems to appear in conjunction with holding the MIDI key, since I often change a parameter for all four tracks, simultaneously. (And no, I’m not mistakenly toggling the MIDI pages).
FUNC+NO doesn’t reset the effects to the SAVED-state of the pattern.
This happens on the tracks and on the external mixer.
Pattern changes in slave-mode come to late (like mentioned above already)
Master Overdrive effects incoming audio on external mixer. Don’t know if it’s supposed to be like that when not set to global? If it is, a separate dry/wet knob for the overdrive on the external mixer would be nice.
I’d love if there was no timeout on the LFO list. I don’t see the point and you have to scroll all the way to the chosen item again if you’re not fast enough.
oh boy - yes - not a bug, but yes it bugs me too - always worth repeating, if only the last selected position was what the encoder went to when you re-engaged the twist when it timed out prematurely … e.g. within 2 seconds still keep a hold of the position you got to
every single time i explore an lfo destination on most of the boxes i’m full of the fear that the menu will hide, it’s not a good workflow
You have the impression of returning to a primitive state in this menu, naked in the forest.
Intense stress, eyes that jump everywhere, erect ears, body hair,
you’re hurrying… you’re just scared.
And when you arrive at the right destination and you manage to validate,
instant endorphin delivery. Russian mountains.
will send them a reminder ticket about both 
