SHUT UP and buy a Tonverk! 
Joking aside I can understand your and all other affected users disappointment.
For stereo sampling etc. I use an old MPC and if I want the Elektron Workflow I grab my OG DT.
i bought mine knowing it wasnât absolutely complete, but i figured it was more of an investment for future musicmaking. that said, bug-wise and QC-wise itâs been a mess. absolutely no reason mono sampling should have been left off of release. i also personally think it wasnât the best move to release the DN2 alongside the DT2 so close, especially given how rushed the Overbridge update was, but hey.
i know itâll be a great machine eventually (and for my studio, itâs quite literally almost perfect), but for the amount of money everyoneâs had to spend to get it, i understand why eventuallyâs just not good enough.
9 Likes
i agree and this is why i sold mine
youâre right- itâs difficult to imagine that throughout development, no one at elektron or anyone beta-testing the device mentioned that the grid machine is defective (especially if a user like @zhelnerovichda was able to kindly elucidate whatâs wrong with it using easy-to-understand waveforms)
itâs crazy bc while using dt2, i thought a lot of the wonkiness was due to user error for months and was kind of beating myself up over it
i didnât realize that it was due to actual bugs until it was confirmed by other users on here (thank you everyone!)
i look forward to hopefully buying it again if these issues ever get resolved though
3 Likes
Hi everyone,
I would like to share a couple of bugs Iâve encountered.
-
Trigger keys do not blink when RTRG is p locked (alone) on a specific one. The trigger keys do blink when any other parameter is p locked.
-
When activating chain mode PTN>FN+Y>C1,C2,C3,etcâŚ>Y:confirm, the sequenceâs length changes for all patterns (in my case went from 88 to 120 in Global mode), its position in the sequencer is displaced and some parameter locks are deleted from trigger keys.
My unit is running on firmware 1.03A, connected via Overbridge to Logic Pro on a Mac mini M4, os Sequoia 15.1.1
I wonder if anyone else has noticed this?
Cheers,
Adrian
Sure, not buying the thing until it is acceptable would be the best way to avoid frustration, problem is that when you buy the next DT2 with rings and bells about stereo sampling etc, you don´t really expect that something as simple and standard as mono sampling it not there 
specially when it is already on mk1 right?..until you buy it, realize is not there⌠and expect in a naive way it will be fixed on next update, to expect this is not that far fetched⌠or maybe it is? 
2 Likes
Are you still dealing with this issue ? I also noticed last night (running 1.03A) that the same audio coming in from my phone was much quieter through USB than through the line inputs. Strange though because when observing the levels in the recorder menu, both seem equivalent (and quite high).
This reminds my of the behavior for line inputs before they fixed the levels issue (in 1.02 ?). Perhaps the fix overlooked USB audio input ?
hello guys,
I got my digitakt a few days ago. The machine is just fun. Now Iâve noticed a serious error and I donât know if itâs my fault or a bug in the firmware.
When Iâm in recorder mode to record a new sample (regardless of whether itâs external or resampling - internal), everything is recorded and digitakt asks me to save. I enter the name and when itâs finished saving, a high-frequency sine bleep comes out. The sound doesnât go away. Only when I turn the device off completely.
Has anyone else noticed the same problem? Itâs incredibly annoying because it doesnât make recording possible at the moment
Hi @lepaaaa you need to upgrade to the latest firmware, which has a fix for this.
Download and details are at the Support page of Elektron.
3 Likes
Iâm still getting artefacts / dropouts when using the standalone Overbridge app. Anyone else? Trying to eliminate buffer settings and such
Donât know if this will help anyone but I transferred about 4gb of samples to my DT2 and it failed about a quarter of the way through. I reformatted the plus drive and made sure to remove all of the non audio files from the folders. I had a ton of older .asd files throughout from Ableton that it seemed to be choking on specifically. After I scrubbed everything it transferred fine. Iâm on Mac OS Seqouia btw.
1 Like
Not a bug so much as a quirk.
[AMP]+[PLAY/CLEAR] gives you Mode=AHD with ATK=0, HOLD=NOTE and DEC=64
[SETTINGS] -> [PATTERN] -> [CLEAR] does the same for tracks 1-8 but for tracks 9-16 it sets Mode=ADSR with similar ATK and DEC. Same difference in track setup if you create a new project and use any pattern other than A01.
Possibly tracks 1-8 were meant for perc/drum, and 9-16 for melody ?
EDIT: Came across this anomaly as I frequently do [SETTINGS] -> [PATTERN] -> [CLEAR] after creating a new project as part of removing the default kit.
Please report this to support directly via a ticket; they still havenât normalized / initialized the behavior of all 16 tracks properly even though theyâre supposed to be identical. Iâve found some irregularities like this as well.
This is weirder than I thought and looks more like a bug. If I start with a cleared pattern, set a short release (10) on an AHD envelope, on track 1, then copy paste the amp page to tracks 2-8, all is good.
If I then paste that same amp page to tracks 9-16 it doesnât work, paste does not happen. The envelope stays as ADSR and there is no change to decay or release. ADSR mode seems to be âstickyâ
Now that IS a bug.
2 Likes
Definitely.
There is something strange about the way they initialize audio / MIDI tracks that isnât quite right; I suspect that some legacy code wasnât considered when making the tracks freely configurable in the DT2. Somewhat related: MIDI tracks sometimes donât get all of their parameters copied / pasted properly (or retained when freezing Euclidean sequences). I donât know if this different treatment is due specifically to the difference between audio / MIDI tracks or whether it depends on them being track 1-8 vs 9-16, but theyâre not being addressed uniformly in some cases.
1 Like
I just witnessed this again on a DT2 running the latest 1.03A firmware yesterday. Not only was a second sound triggered upon release of the same button that was pressed, but it was a completely different sample than the one assigned to the channel.
Rebooting was the only action that made the behavior stop. This bug has not been fixed by firmware 1.03A.
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.
1 Like
I recently purchased a Digitakt 2. I noticed the following problem. First, I loaded several samples into a new, empty project. I loaded these into different banks (A-H) for a better overview. The RAM is about 40% full for the project. Now I loaded an Amen Breakbeat into track 16 and assigned it to different trick keys using Slice Grid via Random Lock. I then assigned more samples to tracks 1-7. I let the song I had created so far play while I selected a new sample for track 8. Now comes the problem. When I listened to which sample might fit the song, the selection suddenly jumped to a different sample. For example: I turn the encoder D and it should change from sample A023 to A024 but suddenly it jumps to A012. At first I thought the D encoder was defective, but the same thing happened with the arrow keys. If I stop the song from playing, it doesnât happen.
Either the CPU is overwhelmed or something is going wrong with the command addressing.
Gee, anyword on when they are going to fix this Firmware update?
Iâll be giving it a big swerve until a stable version is released!
1 Like
Give them a chance, itâs only been out eight months.
Oh.
4 Likes
Looking at getting DT2 but this is a bit concerning. Anyone know if it has been fixed?
No it hasnât been fixed
1 Like