Digitakt II: bug reports

more MIDI bugs:
OS: 1.03A
system settings: MIDI In = USB + MIDI
input: external keyboard via MIDI cable
track : MIDI Machine
recording mode : LIVE quantized / realtime recording of e.g. a melody

problem: missing notes / hanging notes

when recording patterns that are longer than one page, the recorded notes would sometimes get stuck - the note-off information wasn’t recorded correctly. this often happened with legato notes between two sequencer pages.
same with missing note(s), this usually happened at the turnaround of the sequence when the first note of a sequence was played before the first beat.

3 Likes

Ouch

1 Like

Not an insult… what else do you call bugs that have supposedly been fixed and then reintroduced?

2 Likes

when copying TRIG page to another track, MIDI note number does not copy correctly.
For example:
note number +2 -> inserted as +1

1 Like

Sorry … my reply was a bit cryptic. The thought I tried to express was ‘That’s an unfortunate slip on Elektrons part. (Maybe their QA/release process needs tightening up)’

3 Likes

Unfortunately I agree 100%. Developers cannot possibly catch everything (I’m an engineer and I sympathize), but QA should catch regressions and definitely the low-hanging fruit. We have no window into the QA process, but I’m guessing that it needs more systematic definition for testing existing functionality alongside improvements. It certainly feels like every enhancement we get comes along with more / reintroduced bugs, and I imagine it’s difficult to make progress when patching regressions so frequently.

I simply don’t have the time to continue beta testing as much as I had been during the initial launch, but the more people that can corroborate bugs and provide detailed reproduction steps directly to Elektron via support channels, the better. I sincerely hope they get it together, as this machine continues to feel like it’s “almost there” each time a new firmware is released.

5 Likes

I think they need to do a complete review of the way MIDI tracks are handled in the new OS. My impression is that since making all tracks freely assignable (audio / MIDI), they forgot to test these scenarios for general functionality thoroughly enough. Another (possibly related) example involves MIDI track notes 2-4 being lost when freezing Euclidean sequences. It feels a bit like the MIDI functionality is a bag on the side when it should be a first class citizen.

We haven’t seen this issue in 1.03 so we would gladly take a test project to reproduce it.

In general - if we can reproduce things, and reports are clear, we can fix it! With that said, vague reports are better than none :slight_smile:

Regarding other of the latest comments I tried to answer most of them in an earlier thread here: Firmware 1.03 for DT2 - Overbridge - #121 by ThomasJ

6 Likes

Hop I get around sending the project this evening otherwise tomorrow through the response to my ticket by Patrik :slight_smile:

1 Like

My DT2 still drops audio after recording a new sample. I’m on the latest version. It’s not consistent like every third sample or something like that. But the audio drop and subsequently turning the box on and off to get the audio back has happened at least 3 times in this last hour long session…

No idea how but yesterday
My machine started up in my latest project which is basically blank except default samples. I think track 16 was midi to trigger Grind synth via midi, routed to audio input.

Tempo was set to zero ( should’ve been 120)
I couldn’t change it , all normal ways to change tempo did nothing
Pressing play did nothing, didn’t even light up.
Sounds could trigger by hand but otherwise nothing.

I checked all sync / midi / audio options but everything seemed normal.

Project was from previous day , no fw updates or other changes.

bidirectional MIDI communication:
i can only get MIDI CC parameter feedback for the first 8 encoders of the FLTR page. parameters from the AMP page don’t respond accordingly. i use reaper/realearn for the bidirectional communication. any studio one, ableton or cubase users who can confirm this?

Hello, the Digitakt2 is great.
but I just noticed what I think is a bug.
the ‘last’ and ‘not’ last condition only works if the pattern is changed on the machine, no tvia program change.
thanks for your help.
\d

1 Like

Yup, can confirm this. Was using Live. Needed to map other 8 encoders on Amp page manually.

DT2 weirder out earlier. I’d been sampling from track 3, which I then trimmed & saved and assigned back to that track, and then it went odd. I couldn’t get sound from any track and the playback cursor on the SRC screen was like it was stuck and glitched. Switching it off and on, everything was OK again

1 Like

thanks for testing!

Weird one, I’ve lost sound in some scenarios as well after attempting to record.

I have to say this is the most I’ve ever rebooted an Elektron device.

3 Likes

yep it’s a rare occurrence, but happens to me too, and I dunno how to reproduce it :confused:

Hi All,

I’m sending audio via usb c from the OP-1 Field to the DT 2 and sampling it without an issue but the moment I save the sample and assign it to a track ALL audio coming from the DT2 stops and I have to power the unit off and on to get it to come back.

I’m new to the Elektron world and the DT2 is my first purchase. I’ve searched the forum and have not found anything about this topic. Is there something that I’m doing incorrectly or would this constitute a bug?

Thanks

This bug has been fixed in 1.03A firmware. Digitakt II OS Release Notes | Elektron

1 Like