Same was for me, had to send it back and get fixed. The service was super quick since I am in Denmark. No more issue after that. It could be also that they just installed a beta software to solve it 
1 Like
Helllo Tomas, hoping you’re doing great. Please count on me to test the beta version
1 Like
I’m trying to save MIDI presets for my various hardware configurations, however the DTII doesn’t appear to be saving the TRIG related pages/parameters. I’m needing the MIDI presets to remember the NOTE values.
Does anybody know if this is by design? Or is it a bug?
I hope so, every day I log into Elektronauts hoping to see a post about an updated firmware.
Ahead of getting the DT2 I prepped samples to transfer but I’ve had so much issues uploading them that I just stopped trying and is waiting for a fix 
3 Likes
What issue are you having? I had trouble with transfer crashing when I tried to upload all my samples in one go, but I solved it uploading in smaller batches
About MIDI LEARN: Can anybody from the community please come forward to highlight if there is a successful ELEKTRON DIGITAKT 2 to IPAD Synth combination out there, where midi learn (new feature on Digitak 2 where Digitakt is learning the CCs by pushing the encoder / midi learn is blinking in the display) is working? I can play the ipad synths with the digitak keyboard, change the presets, all working but midi learn does not.
I have a lot of ipad softsyths like moog mariana and some others where i can´t get it to work. I already aware about all midi settings on the Digitakt 2 that were discussed prior in this threat and I applied them. I also ensured that midi CC is sent by the synthapps. Up to now no success.
1 Like
It’s just random and constant crashing of transfer for me, I tried with hub and without, with different cables etc… One sample pack (ish 200mb) would have to be divided in small blocks, so transferering even up to the 8gb that seems to be a limit now is just… I’d rather wait 
Just tried with Moog Model D app on iphone, midi learn working here.
DT2: I’m using track 16 as MIDI track for Model D (note: if you’re using MIDI on DT2’s track 9-16, make sure they’re enabled in MIDI settings, as 9-16 are OFF by default).
Model D: MIDI In and Out both set to ch16.
On DT2’s FLTR (page 2), FUNC+hold the knob to enter learn mode and adjust Model D’s on-screen element (e.g filter cutoff) – the learn is done, stops flashing. Move to FLTR page 1 and twist the knob to control Model D’s filter.
2 Likes
This reminds me… I discovered this recently with one + half modes and phases… they do not seem to work as expected… I assume many people are not using one/half with phasing… I know it took me 4+ years before I noticed!
I was unable to explain what was happening as elegantly as you have, do you think it’s a bug? Or is there a reason for such behavior? Seems illogical to me (and I assume all Elektrons work this way?).
I don’t understand what’s wrong?
They run one time starting at the trigger, and ending, half or full cycle.
Is it not exactly how they are described in the manual?
• ONE The LFO starts when a note is trigged, then runs to the end of the waveform and then stops. This makes the LFO function similar to an envelope.
• HLF The LFO starts when a note is trigged, then runs to the middle of the waveform and then stops.
P-51
1 Like
Play around with the start phase and see what happens especially when you go past 63. I’m not saying it’s definitely wrong more that it seems illogical.
Will give it a try (when I would not be supposed to be working :D)
True that so far I have always used them with the phase at 0
1 Like
ONE and HALF are weird, it’s as though they swap behaviour half way through…
At 64, HALF will play the whole cycle (as you’d expect with ONE)
At 64, ONE will play half the cycle (as you’d expect with HALF)
It’s the same on DN and probably the other devices, so i assume it’s intentional, but maybe it’s a bug…?
2 Likes
Is it time Elektron?
(Too many times online today … it has to be)
1 Like
Hi, new bug (I think) found on my DT2, and seems confirmed by Elektron support : BPM clicks heard on stretch machine especially on the 3-4 last bars on 128 steps sequence.
It’s a bit tricky but I think it’s quite annoying : when recording an exact 128 steps sample and affecting it on a Stretch machine track to play a trig length for 128 steps (so no stretch in fact), there are audible clicks on the last four bars.
No clicks heard when just playing the track trig only.
Ahh, this helps me understand behaviors I hadn’t before: Half, as @Protopia posted from the manual, is going to stop at phase ~64, whole at 127. So yes, they’re going to swap lengths with phase > 64. Knowing this behavior will be helpful to me at least.
I don’t think it’s a bug, @golddust and all, just the way it’s set up, logical at least from the pov of how efficient code would interpret the manual. On several waveforms, Half is an envelope (or for ramp it’s an offset to LFO depth), so it makes sense to me to keep that endpoint behavior consistent.
Still wrapping my head around the ways to use LFOs on DT2, there’s a lot to modulate…
I’m having the same exact issue, I dunno if it’s a bug or I’m doing something wrong.
I’m trying midi learn with ipad, with a syntakt, with a microcosm but there’s no way for me to make it work.
DT2 can send and receive CCs (I’m new to midi, sorry if the terms are wrong!)
There’s just no way to make midilearn to work 
Taking the DT2/Syntakt config:
DT2:
Auto channel set to 10 - nothing else is set to 10
Leaving tracks 9/16 deactivated
Track 8 set to midi on SRC, controlling channel 1 in the ST
If I press 8 on DT2, the kick on track1 in the ST is activated
ST:
Track 8 set to midi on SYN, sending to channel 10
Pressing 10 on ST activate whatever track is active on DT2
So the two machines can talk back and forth but midi learn is dead
1 Like
I discovered another bug with Control All Config, I don’t know if it was published here before.
Sometimes Ctrl+all does not work correctly when trying to use the affected tracks feature. Sometimes it is applied to all tracks, despite the fact that I mark some of them as not affected.
2 Likes
If you’re using CTRL-AL on a track that shouldn’t be affected, is track will still be affected. This, at least, is a design choice.
You can see it as a way to temporarily add a track to the CTRL-AL selection.
5 Likes
Is that by design or a bug ? Sounds like something that could easily catch you out.
1 Like