Digitakt 2 track 6 double hits and not recording

This has been driving me crazy but I finally think I determined the cause of strange sounds are the result of a key on track 6 of my Digitakt 2 will play the src sound when depressed and then on release play a different part of the src sound.
Also discovered the track is not recording in any of the record modes.
Has anyone seen this and a solution?

What I notice of this trig is that like the other trigs the key flashes white when depressed but unlike the others it also flashes white when released.

Any insight is appreciated. Thanks

Hey, that sounds super annoying. First thing I’d probably try, given the conditions you’ve described, is use the test mode as a vehicle for confirming whether or not there is actually some physical contact or other prolonged contact with the switch on that 6th trig which you mentioned as an issue. I think that if it’s double triggering or the light remains as a result of a physical type of issue, then the keys test which displays visual feedback for buttons and encoders (text on the screen will state the corresponding button or encoder which you’re pressing/turning) should show something to corroborate that.

From an off state, hold down the func key and turn on the machine using the power switch. Test mode should come up immediately, then release the func key and run the self-diagnostic. If it’s a hardware related issue, test mode should still say zero errors, in the unlikely event that it shows any errors then it’s possible something software related is going on, but it does not sound that way from your description, but as it’s a unique issue I wouldn’t want to dismiss that as a possibility.

After the self-test, you can start pressing buttons - the standard behavior for the first 2 trigs is usually going to be screen all lit and the other is screen completely dim, this is a pixel test for the OLED. The following 3 trigs usually individually light all LED button lights in RGB colors which allows individual filaments (or whatever the colors are based upon) to be tested in the event only one color has burnt out on a button, there is also a readout on the display that states the name of the button you’ve pushed and it will only be displayed for the duration of the button pressing - once released, the screen should go blank.

What I’m suggesting, is to engage trig 6 if that’s the one with the problem and then watch the display to see if the behavior is the same as the other keys, where as soon as you release the button the text disappears, or if the text lingers which would probably be indicative of a physical connection which still remains present in the tactile switch under the button cap.

Start with that, check the result, and based on that there might be one of a few possible resolutions up to and including having Elektron do a repair. If this was purchased recently through Sweetwater or something like that, they may or may not help you directly but assuming it’s outside of whatever the retailer’s DOA exchange policy indicates, then if it does require repair, Elektron should be the ones to handle it and there won’t be any cost aside from possibly shipping but cross that bridge when you come to it.

If it does seem like a physical delay and you possibly feel like that trig is rubbing on the faceplate when it comes back up, use your phone light or something which is bright enough to get a good look around the trig itself and see if one side of the button or the corner of it is maybe getting hung up on the cutout, if it is that might be something you can resolve on your own however you don’t have to because Elektron does owe it to you to take care of it and if you want to document a repair history then I’d just let them handle it as long as you have the time to wait, otherwise something like that can usually be resolved by realigning the upper PCB but is done at your own risk by opening the machine.

Again, cross that bridge when you come to it. If you tell me what happens in test mode, I’ll do my best to help you hammer out a next step. Hopefully it’s nothing major but it does sound like a pain in the ass so better to take care of it now than later. Good luck.

2 Likes

What an amazing response and full of great information. I’m going to perform everything as you suggest. So, thank you for that.
This morning as I thought more about this I decided to see if the issue would appear while using OverBridge. The problem did not happen once while in OB and when I stopped using OB it has resolved. No double hits or odd trigs. It’s probably a bug?
I know I have power cycled the unit numerous times while trying to understand the issue but once I utilized OB it has worked fine for hours now. Bizarre
, but I’m glad it is resolved.
I’ll test as you proposed. It is really great information. Thanks again!

1 Like

Well, I think that it’s fantastic if it’s stopped doing that on it’s own after connecting to OB but still leaves a bit of a mystery. I’d like you to take a look at the firmware version which shows on the display when you first turn on the machine, if it shows anything other than 1.03a then I’d encourage you to update.

I looked at the release notes from prior firmware versions and on 1.01a a bug fix is mentioned regarding double trigging so it could absolutely be a bug if you’re on that earlier OS or anything below current.

Hopefully a firmware update is all it takes if they already squashed the bug. Good catch on your end!

Quick link to the resources page:

Digitakt II | Elektron

If you’re up to date, I’d encourage you to report it as a current bug so that they know it wasn’t resolved with the fix, especially if you see no physical issue with the machine. Really hope for your sake that’s all that there is to it! Simple solutions are the best solutions.

2 Likes

Hi, have you been using midi with the Digitakt? I have had a similar issue with my Minifreak playing a notre and switching tracks on the Digitakt. When pressing one of the affected pads, on release it will play that note; The issue stops when I play it on the Minifreak again. My guess was that there is a missing note off. But your issue sounds like it is probably something entirely different.

Hey, considering that the issue you just mentioned has a similar kind of behavior to what we’re talking about here, can you confirm whether or not you’re already on the current firmware? I would definitely update your device if you aren’t on 1.03a and then check for an improvement.

Hi, thank you for the reply.
Yes, I am currently on 1.03a.

1 Like

Ok, if you think it may have to do with a missing note off or a recurrent note on, then, if possible, you should see if you can use a midi monitor app in order to see what the Digitakt is actually sending. If it looks like something unusual then it might be easier to troubleshoot where it’s coming from and should probably behave in a predictable fashion once you pin it down, most bugs are usually only a mystery until you figure out the conditions that bring them on.

Not sure I can help but I’ll see what I can do, and at a minimum if you figure it out then it can be reported and validated for a future fix. Also check out the digitakt II bug reports thread and see if anyone else has already reported something similar, that might also help validate the issue. Good luck to you as well!

And just to be thorough I checked and for both of you this is possibly relevant:

To complete the quote, the tail end of that post says:

“EDIT: I recently got word that the team is aware of this bug, and that it’s being worked on. It’s related to sending notes from an external MIDI controller on the auto channel while switching channels (extremely common if you’re using another sequencer for MIDI input). No word on when that might be in a firmware update.”

So, Sonarman, even on the current firmware if midi is involved this could be the issue. Sounds an awful lot like what you initially described.

1 Like

Yes. 1.03 A. Thanks again and I will write up a bug as I think this same issue happened on another trig key but at the time I thought it was a sound artifact. The device is still quite new to me so noobs no see problems nearly as quick as pros!

1 Like

It’s more than that, you shouldn’t really need to play guessing games with weird behaviors on your new gear in the first place but regardless, I suppose that’s just the active situation at the moment.

If you currently have access and are able to login to your account on elektron.se then I’d probably message them about this issue directly via the contact form, so that if they have any working solution which is not known on the user forums, you’ll have quicker access to it.

Definitely specify that you’re on the current firmware so you don’t have to waste a back and forth email with them asking if you’re up to date.

Not sure I can do much else at this point, but I hope it won’t be too inconvenient for you to work around it, at least for the time being.

Also, if they do have a solution for you, it would be super helpful if you could update this post with that information, thanks.