Digitakt II: bug reports

[cedward4]

Left it for two hours, no luck unfortunately.

[Hawk]

I have also experienced this bug and reported to Elektron directly. I sent them my project and they confirmed the bug, which they thought had been eliminated in an earlier firmware. They told me they have reopened the issue and are working on squashing it.

[ripsaw]

When entering a preset name it will let you enter 16 characters, however it will only save the first 15 characters

If you then go to save the preset again in a different slot, it will show the 15 character name and a chevron >> under the end of the name entry field.
If you scroll to the end it will show the 16th character entered previously and remove the >> but still will not save a 16 character name.

[dialectrics]

Not sure if bug or planned behavior, but in +drive sample selection menus if you press and hold func and move up and down, the first press moves a full page but you have to press func every time to keep moving by page.

I swear on DT1 if you held func every up or down moved in units of pages.

[new_drugs]

I apologize if this has been mentioned but my Digitakt 2 just froze up while I was trying to select unused samples in a project’s Ram. The project Ram was 99% full at the time. After it froze I turned it off and back on. I tried it again with the same result. Not sure if it is just my machine.
Edit: I manually selected and unloaded larger individual samples from the project Ram and then tried to again select all unused samples and again had the DT freeze.

[ripsaw]

Same here. 66% ram usage and “select unused” freezes the device.

[new_drugs]

Thank you for verifying! Much appreciated. Maybe there is something I’m missing in the manual or on the forum but if this is an as yet unknown bug it could be pretty bad if you go to remove unused samples from a project and you haven’t saved your work in a while.

[ripsaw]

When using song mode I’m getting ‘phantom triggers’ inserted in tracks I’m editing.

Edit: see below reply this is likely an artifact likely caused by track swapping not song mode.

These are red trigs that don’t do anything, they don’t trigger a sample, they don’t alter any parameters, they blink like there is active p-locks, but again, they are red, not yellow, samples that are playing (that would be cut off if a trig were there) continue to play. It’s like there is not a trig there at all.

Any interaction whatsoever makes them become ‘active’ and solid red, no p-lock indication blinking, they start acting like a standard trig would.

Has anyone had anything similar?

There is no midi or USB going into the device, no cables connected so I doubt there is any errant midi getting in and causing the issue.

[ckx]

Yep this happens to me frequently, started after the last update and I still haven’t figured out why but it’s incredibly frustrating. It doesn’t have to do with song mode for me at least because I never use it. I thought maybe it was linked to track swapping, as after I use it those tracks/patterns seem to start producing ghost trigs… but honestly I’m not entirely sure.

Also curious if anyone else has had this issue/knows the cause.

[ripsaw]

@ckx

I thought maybe it was linked to track swapping

that could be it, I re-organized some tracks when I was doing an arrangement in song mode.

If any of the elektron devs are reading this thread, I can provide a stripped down project with the issue present.

[ripsaw]

Going into save a Preset or Kit, on the screen where you choose what slot to select to.

If you press TRIG/SRC/etc page buttons it does not forward you to that page. You are still on the file save dialog, you can still scroll up and down, but will be unable to press ‘YES’ to save. To get out of this state you have to press ‘NO’ to back out the screen and re-enter it to be able to save.

This issue is not present when saving a project, pressing the TRIG/SRC/etc page buttons actually kicks you out of the save dialog and shows the requested page.

[ripsaw]

When loading presets the search function does not work correctly. The first time you go in and search for ‘text string’ it shows files containing ‘text string’

If you re-enter the loading screen it will show:

SEARCH:‘text string’ FN+NO: CLEAR at the bottom

But no filtering based on ‘text string’ is applied.

This exacerbates the issue where to preview new sounds in context they need to be loaded instead of automatically previewing with whatever trigs exist on the track.

To in context preview a sound with ‘text string’ you need to

1. enter load preset
2. go to search page
3. choose preset
4. re-enter load preset
5. re-enter search page
6. choose preset

this could be made a little easier by remembering ‘text string’, as the GUI suggests is the intended function. and even easier still if trigs on the current track previewed the selected preset.

[bigdave]

Yeah glad I saw this I thought I was having hallucinations! Loads of red flashing trigs. Ghost trigs. Happens to me pretty regularly.

I learned to embrace track chaos and so have only ever used track swap once to try it out so I doubt its that for me.

[djst]

In case it hasn’t already been reported: when previewing a trig by holding the trig and pressing yes, if you release yes before the trig, it works fine, but if you do it in the other order, the trig behavior menu shows up.

Feels unpredictable and actually took me a while to even understand why it sometimes interrupted the flow. I don’t think that menu should ever show after just previewing a trig.

[gelabs]

Troubles with DINSYNC :

Configure MIDI THRU port to output DIN24 → output OK.
Save, reboot → No DINSYNC output.
Go back to MIDI Config → Port Config, switch to MIDI or DIN48 then switch back to DIN24, and now it works.

It would be nice to have this working without having to reconfigure the THRU port each time.

[ripsaw]

This was tapped by @shigginpit as the cause of an issue that manifests as “time between triggers is never consistent” even though it does not logically make sense.

I went and tested anyway. Both using “start” and using “threshold” as the trigger at 120 produce perfect length files as confirmed by loading into ableton and turning warp off. So this never was the cause of the issue, because it has already been fixed in a firmware update. (and incorrect timing for the total length would not cause timing inconsistencies between triggers to begin with.)

For more information on the “delta time between triggers is never consistent” see the following thread, it could save you some major problem solving headaches in future:

Digitakt 2 Clock Stability / Jitter Tested. Delta Time Between Triggers Is Never Consistent

The playback time between each trig on the Digitakt is inconsistent, even with no micro timing present. There is jitter. If you playback/record two tracks from the same project in two separate passes each pass will have it’s own inconsistencies and the two will not sound as tight when played together. I wanted to find a way to show this on device, one that completely removes any external influence, so no midi clock jitter or interface jitter. This also allows you, the reader, to run this test…

Note this is present on the DT/DN/DT2/DN2 they are all running the same processor. I doubt that will be fixed in an update.

[Hawk]

Have you submitted this issue to Elektron yet?

[ripsaw]

as I said over in the linked thread:

@ripsaw

I don’t think this is a bug, it’s a hardware limitation.

I just recorded my DN2 directly into my DAW and it too has the exact same jitter as the DT2.

The Digitone/takt 2 share a CPU, the same CPU as in the DT1 + DN1 and people had the same issue with the DT1 and jitter as seen from the threads I linked before.

it looks like this is just how the hardware is and you need to keep it in mind when doing exports.

Also no one has responded to the last several things I’ve sent in. I’m waiting to see if someone is actually alive bothering with the DT2/DN2 platform over there.

The one thing that I did end up getting fixed, applying a mod source to playback type was fixed because I reported it in the bug report thread we are in now.

So far this thread: 1

Email: 0

If you own the device you are free to send an email about the issue, I’ve given instructions over at the other thread to perfectly replicate it, and see if they get back to you.

I went ahead and sent a link to that thread. Lets see how long a response takes.

[Hawk]

It sounds like you have already found some good data, please go to the Elektron support page, write them a short email, and link to your thread where you have described the issue. That is how you will bring it to the attention of the devs, and hopefully they are able to improve the behavior you are seeing.

The “bug report thread” is unofficial, it is much better to write support directly from the support page.

[DEEPMOSES]

I’ve just submitted a support ticket as I all of a sudden noticed that key 15’s led was acting up. The red trigs stopped working, or they still worked but the red led was not. A test confirmed it. Annoying but still usable. But now I’m noticing more strange behaviours:

• Red trigs needing multiple presses to turn off.
• Extra trigs randomly appearing on tracks.
• Trigs not playing until they are auditioned with FUNC+yes.
• Settings like Velocity being set to 0 on all tracks on one pattern.
• Control-all still affecting parameters on tracks where it’s turned off in config, but only on some patterns, not others
  Etc…

Has anyone else experienced any of the above?
Have they been reported?

Cheers!