Thanks.
Hrmmmm…do we have any clue if they are even entertaining this feature? I haven’t hopped on any AMA’s nor have I been following this since the last update which still hasn’t resolved the Attack ‘pop’ issue when I try and play slices in a loop on the grid machine—they acknowledged the bug but never fixed it.
USB set to EXT doesn’t work since 1.03A. Elektron working on a fix.
I downgraded to 1.02 but the USB EXT level is -15 db compared to USB MAIN with IN LR maxed.
The last update (1.03/1.03A) was about Overbridge only I’m pretty sure, nothing else mentioned in release notes.
@ThomasJ recently posted some news about some of the work in progress.
But with USB AUDIO consequences apparently. See my post above.
List of changes from OS 1.03 to 1.03A
Bug fixes
Saving a sample could, in some circumstances, cause audio to stop working.
The input level was too loud when using Overbridge to send audio over USB through the FX.
No, not connected to any computer, no usb connected, only a single midi in from Roland MX-1 for clock start stop. Issue only occurred since 1.03, have rolled back to 1.02 and problem resolved.
No computer connected, only midi clock start stop reset from MX-1, rolled back to 1.02
This is also a great reason to add loop crossfade!
I’vr been getting around 1shot start pops by adding the least amount of attack I can on amp env, but that wont help for looping slices. 
Honestly yours is still an issue on OT which does have start point adjustment on slices. Best of luck.
repost in case this bug slipped through:
my usage scenario is as follows:
digitakt 2 used as MIDI controller + sequencer / daw used as sound module
digitakt is in overbridge mode / daw: reaper / realearn is used for parameter feedback for the CC knobs. (realearn has additional options to prevent echo feedback of midi cc information. i didn’t monitor any suspicious outgoing or incoming midi information from the dt2.)
after recording a few tracks of midi information (note only, no CCs yet), the machine freezes and needs to be rebooted.
in firmware 1.02 I had a problem when recording MIDI CCs in realtime REC mode: overdubbing caused the OS to crash. no parameter feedback was used. dt2 acted only as a MIDI controller and received no MIDI data from the DAW except clock information. i can’t remember the exact MIDI system settings because i tried different configurations to get rid of the problem.
i found this warning in the manual: if MIDI+USB is selected in the OUTPUT TO settings, MIDI data will limit the USB speed. when sending large chunks of data, make sure you only use the USB setting.
at the very least, please make sure that crashes are avoided when there is a problem with a data bottleneck even when MIDI+USB is selected.
thanks a lot, your work is appreciated.
Found a very odd bug since the 1.03 update. The external mixer is stuck in a non existing global mode (inverted graphics) and seems to be set to dual mono mode without having two separate pages for L and R. Even more bizarre is that the sampler can only sample in mono now for the external inputs. Which is both weird and eh useful sort of sometimes 
I think the cause of this oa that I’ve been working on a project that started on the original DT and I might have set the global mode to ON for the external mixer in that project.
Weird thing is though that this was not a problem in 1.02 and it showed up when updating to 1.03. Reverting back to 1.02 also solves the issue. 
also reported through a ticket to Elektron
Regarding the screen issues, has this still been occurring on recently purchased units? Seems like this has been ongoing for a while, going back to the Syntakt.
I’d prefer to buy a DTII that is coming from the assembly line already fixed, rather than buy one that is much more likely to go bad and have to send it in.
Yeah, this bug still exists in 1.03 firmware. When bpm is 30.1 the delay time is correct but at 30 bpm it’s not.
I see that the latest Firmware version is 1.03A
Does this new firmware update resolve the prior issues?
I’m still running 1.02 — should I just stay on it for now? I wanted to test Overbridge — should I perhaps hold off on that? 
Im staying on 1.02 for a while yet, 1.03 only added overbridge and bugs. 1.03a fixed a horrible sampling bug that was added in 1.03 but there seems to be other less glaring bugs also added/persisting.
I need overbridge less than I need more bugs so I’m its 1.02 for me for a while yet.
Good call. I’ll follow suit — despite being very keen to get into OB.
No issues in mine, just got it last week…
This issue is still occurring. It appears if any device was made in Poland there is an increased likelihood of encountering the screen issue. All digitakt 2s are being built in Poland. There was a digitakt 2 recently posted here with 2024 build date that has this problem. So the issue is still present. We might even see some Digitone 2s start encountering this problem as those too are only made in Poland.
Thanks for that info!
I have a DT, which I am keeping, but really wanted to feel good about buying a DTII.
This makes me feel like holding off. Bummer.
I wonder if this bug has revealed that they’re currently working on functionality to finally sample in mono. Though I find it a bit strange that code for an unreleased feature has made it into production firmware!
I think I’ve seen this a few times as well. @ThomasJ is this something that can be added to the list for imported DT1 projects? Some of us are still running into bugs on these.
Dave, this is exactly the type of bug I was describing to you on FB the other day (under a different account name) when we had an extended back and forth. So it’s happening again on 1.03A?
I’m staying on 1.02 for now, for exactly this reason. I reported this at initial launch and it was supposedly “fixed” but now I’m not convinced… I think there have been some regressions based on what I’m reading from others who have updated.