Just submitted a ticket.
1 Like
If I save an empty kit in a project with all samples unloaded from ram and load it afterwards it loads the default samples into the project
Regarding to the manual it should be possible to arm the sampling using the following shortcut:
Unfortunately, this doesn’t work in reality. At least not, when R.START = PLAY. Either this feature is poorly described in the manual or it is a bug.
In general, I find it impractical to toggle an option such as ARM, which has only two states, via a rotary control.
2 Likes
Is everyone else’s screen ok? Mine is going back to Thomann tomorrow. All good when it arrived but after less than a week of use the screen is displaying corrupted pixels (a vertical line of ‘overbright’ pixels on the left and a horizontal line of dim/fuzzy pixels near the bottom). Hopefully a replacement unit will be ok!
My screen is slightly weird sometimes. It’s like, if there’s a portion of the screen that has a bright part, like a background highlight, then everything else to the left or right will be slightly dim, or certain pixel lines will be dim. Not sure if this is just how the new white screens behave or if it’s a defect.
1 Like
R.START = PLAY will start the recording when you hit PLAY 
, if the recording is ARMED that is. So, no bug here.
I would love it to ARM the recording so that it starts the next time the trig 1 plays, but this is a feature request I believe.
2 Likes
SAMPLING + YES doesn’t seem to work; it behaves as YES.
Seems the same for both modes, not sure…
1 Like
Hello
I got the DT 2 today but I have a problem with the panning. No pan left and right when I turn the pan knob in AMP section. I use a headphone plug into the headphone output.
Do you have an idea? THX
First thing first: try other headphones, if possible with no intermediate adapter.
I’ve tested my unit and it’s working fine.
I know what R.START = PLAY is. I’ve already been using it for two or three days 
We need to arm the sampler everytime before we hit play to start the sampling. My issue is the non working shortcut SAMPLING+YES. I don’t want to turn a knob everytime I want to arm the sampler. All I want is to enable ARM using the shortcut described in the manual. And this doesn’t work …
1 Like
It’s definitely not normal for the ‘white’ screen, assuming it’s the same screen as the Syntakt (my Syntakt shows none of these symptoms), but I wonder if they changed suppliers for the D2?
Mine isn’t ‘sometimes’ either, it was fine when it arrived but less than a week in I have 2 consistent bright/dim/fuzzy lines on the screen in the same place every time I start it up. If it’s like this after a week I’m not prepared to put up with it in case it gets worse - Thomann sent me a returns label - it’s going back tomorrow 
Oh, my bad.
Definitely a bug.
3 Likes
Could you post a pic?
Here’s an example of what I see. You can see the left half of the screen get darker whenever something on the right side is highlighted. Some of these screens work by letting you invert the pixels of a portion of it (like for a selection), and it almost feels as if using the invert function messes with other non-inverted pixels in the same rows. I also have a few rows that are permanently slightly dimmer than others. Most of this is pretty subtle, but makes it feel like I’ve had the device for years instead of days!. 
1 Like
I have this too, I remember this also happened on some versions of Digitakt I
This is normal. My DT2 and my old DT has the same ghosting “issue”.
With regards to the person you are advising it is normal/expected, officially too it seems, see post below mine here …
it’s not considered a fault, it’s an aspect of illuminating the rows of this particular screen type … nothing to be glad about but nothing to sweat either - all units will almost certainly behave this way fwiw
2 Likes
It works in both cases for me, whether the device is stopped and R.STRT = Play or whether the device is playing already and R.STRT = Thresh
In both cases the SAMPLING icon is primed gold/yellow …
You are not ‘meant’ to be using this shortcut when in the sampling page already as the YES functionality is for recording and arm is a twist away
!|!|! PLUS YES was afaicr only meant to be a speedy ‘REMOTE’ way to arm instead of having to pull up the menu with !|!|! THEN YES
so that you could do this record priming in the same way that the DT1 could
Perhaps if this context awareness is the intended caveat to usage it could be clarified (if not already, which it doesn’t appear to be, this functionality was a late addition btw)
3 Likes
Here’s a summary so far:
Digitakt 2
Screen glitches - UI issues
Low external input level - awaiting fix
Transfer is very slow over USB
Transfer crashes / fails
+Drive becomes corrupted requiring reformat
Amp level jumps up when adjusting whilst playing a sample
Cant change mixer settings on imported projects + When importing DT1 projects (with global FX/Mixer enabled, might be related), the external mixer view ends up in a weird state. Labels are inconsistent (and all with a white background ) and dual mode switch is stuck to disabled (although audio is affected if I turn the associated knob).
Previewing samples both from the sample load interface and after recording a sample, do not transmit audio over USB
werp machine in digitakt 2 produce some annoying crackles compared to digitakt 1
UI bug : SRC slots list popping up after SRC button press. Persists after reboot.
Slice mode bugs
Fun + retrig speed always 1/16ths
Changing filter type while an LFO is routed to a selectable filter type parameter will visually display the new filter, but the one routed to by the LFO will still be in effect
After sample is recorded zoom behaves differently on start and end point. Start point seems to follow zoom setting while end zooms in 10x the track.
After a double stop Delay and Reverb aren’t sent for Inputs without audio track trigs. Chorus is sent.
if you hold a note in keyboard mode, play a 2nd note and release it, it triggers again the first note.
Can someone verify this bug? The audio waveform is not being updated when changing patterns.
How to replicate it:
- Start a new project
- In pattern A1, track 1, place trigs, in my case, on 1, 5, 9, 13 (four on the floor)
- Go to pattern A2 and do the same thing, place trigs on track1
- While still on A2, change the sample for track 1 to anything else
- Press SRC to visualize the sample audio waveform
- While the Digitakt II is playing, change the pattern back to A1, then A2, repeat
The issue that is that the audio waveform is not being updated when changing patterns.
Error when trying to rename a sample that I recorded after I saved and I just got an ERROR popup.
The sample is not used anywhere and is not write protected. Renaming it with the Transfer app seems to work.
Could you with a Digitakt II test if you also get an error?
Steps to reproduce:
- FUNC + SAMPLER
- Select +DRIVE
- Select recorded
- Press the right arrow key on a sample and pick RENAME
- Change the name and press YES
After step 5 I get an ERROR popup in the middle of the screen.
non working shortcut SAMPLING+YES. I don’t want to turn a knob everytime I want to arm the sampler. All I want is to enable ARM using the shortcut described in the manual. And this doesn’t work …
Midi bugs
Midi Learn doesn’t work with AUTO CHANNEL? It works with the track channel specified in MIDI CONFIG > CHANNELS
Elektron need to thoroughly retest midi track functionality and bugs in that area, I ran into multiple bugs listed below. It usually starts off working fine and then it goes sour.
- Tried saving midi track preset that I made on track 9 and Digitakt froze, had to reset
- Midi buggy in general, can work one minute, then switch pattern stops working when returning, no midi data been picked up in Ableton. When loading a midi preset that was previously saved it doesn’t work.
- On reboot midi tracks work again, but if I go to a new pattern and load my midi preset, midi tracks stop working on all patterns until reboot.
- Track 16, Val 13, 14, 15 on midi track dont send midi date at all, even after reboot.
- Digitakt crashed again when trying to load preset (conflict with midi track behaviour?). With midi track preset loaded on pattern 16 bank 2, this happens every time after rebooting.
- I loaded midi preset on tracks 9-16, after rebooting only track 9 would work.
- Note: I am sending midi via channel 10, cc numbers 16-32
I have a bug on all my projects with midi tracks transferred from my OG DIGITAKT.
On my midi tracks controlling external hardwares, when I launch playback for the first time, there is a glitch on the first step.
It’s doesn’t occur when I launch playback a second time for the same pattern.
It sounds like a bug messing with midi messages send for retrieving bank/sound bank on external hardware.
I can´t get the FX control via MIDI CC to work. Let´s say I set the fx control channel to 16 and try to control the master overdrive (CC 17) with my Faderfox EC4. Nothing - and nothing for other master fx parameters (ie compressor) either. Control works fine for individual track CCs though.
I have an issue with MIDI LFO :
Destinations are never restored properly after a temporary save / reload, loading a project or rebooting the unit.
They can even be set to invalid destinations (like LFO 1 depth modulated by LFO 1) depending on the value during the save.
I can reproduce it on OS 1.01 straight after an empty reset, by simply creating a midi track, setting a destination and saving / reloading to temporary.
Unstable midi clock when USB is connected
20 Likes
Anything official Elektron can tell the owners, existing and future, of DT2 regarding file system corruption bug yet? That would be great.
4 Likes