Digitakt 1.11 : Bug reports

Elektron Gear Digitakt
#113

Hey guyz, I’ve been battling with a bug for a few months and just sent a ticket to Elektron. Thought I would share to see if anyone would be able to replicate this. I’m too lazy to re-write the whole thing so this is just a copy/paste from the ticket :

I’m running OS 1.11 and I use my Digitakt for live looping, I usually use my Keystep to play different DT tracks. I do all of this as the sequencer is running and I quickly switch between MIDI channels on the Keystep. The issue is that sometimes I will play the full cycle of my melody (64-steps long) but when the sequencer reaches the end and starts over, the first notes won’t playback. Only the second half of the melody is recorded and plays back.

So far the bug was not very consistent. Sometimes it would never work and I would have to play the full melody twice to be sure it would be properly recorded, some other times it would work as expected. However, I think I discovered the origin of the problem yesterday! This happens when the highlighted on the DT has a shorter length than the track I’m recording on. For example if the track 8 is selected on the DT and has a 32-step length, I won’t be able to record a 64-step melody on track 1 properly.

Here is a step-by-step guide to replicate this bug on a blank project (you will need an external controller, I use a Keystep) :

- Create a new project
- Enable the Length per track option on the Scale page
- Set the length of track 1 to 64 steps and the length of track 8 to 32 steps
- Set the M.LEN to INF
- Exit the Scale menu and highlight the track 8
- Now put the metronome on and simply press Rec+Play, record some notes with your MIDI controller on track 1 which is the kick by default
- If everything goes “well” the first 2 bars or so won’t be recorded, only the second half of the pattern will play

If you wait for one full cycle before playing some notes, the pattern might be recorded properly, but that’s kinda random in my case.

Any input on this? Am I right to assume this is a bug in the first place? Cheers<3

#114

Is this related?

Best regards,

Gino

#115

Hey Gino, thanks for your input! I wasn’t aware of that problem, that’s kinda weird but I can imagine how changing the track length could mess up with the metric of it all. However in my case there’s no sudden length change, I set the track lengths before starting the sequencer at all. Also what’s weird is that the DT doesn’t behave the same depending on which track is highlighted, that’s the main thing that makes me think that it’s not “working as designed” but who knows!

Anyway thanks again and have a great sunday. :slight_smile:

1 Like
#116

Same here !
I have the same behaviour here.
my problem is if I use different scales for 2 tracks I 'll end with the first step on one of the tracks to have buggy restarts of the pattern. I can hear delay between tracks that seem to correct themselves a few steps later.
on the pattern I am working at the moment, I have 64 steps with 1/2 dividers on one track, 64 1/4 on a second one and only 16 steps 1/2 on the next one.
I should mention that I tried to set master length parameter to values 64 / 128 / 256.

this problem only exists if I set the different tracks to different lengths/ scales.
once a pattern’s sync is “corrupted”, I can only work with it in “scale per pattern” mode ie same number of steps / divider on every track.
I tried to find a workaround without success.
I submitted a ticket today.

#117

Okay so I found something funny regarding the LFO speed, I’m running 1.11 since a few days because I couldn’t be bothered to update haha.

I’ve got a sequence at 152 bpm with a sample running on track 8, the sample fully covers 32 steps. The LFO is routed to the overdrive and should be accentuating all the 16ths. SPD is set to 32.00 and MULT to BPM 64. That’s all working good and fine.
Now when I introduce another track with a different LFO speed, the LFO of track 8 somehow goes all out of sync. Specifically, I use track 3 which has got the SPD at 51.43 and a non-bpm-synced MULT set to 256.

According to the manual, the non-bpm-synced MULT assumes 120 bpm; I suspect these different bpm settings conflict, so that track 3 somehow influences the MULT on track 8 with a wrong number or something. It’s kinda weird that one audio track influences the behaviour of another.

Is this a known issue? Is it even clear what I’m talking about?

1 Like
#119

It happens whenever you enter per track scale from a pattern multiplier other than 1x. To fix it, just revert back to your original state, and switch to x1, and then enter per track scale.

1 Like
#120

Hi! Thanks for the reply, but I don’t understand what you mean. How do I revert back to original state?

#121

Revert back to original state = Reverse engineer to the state before you initiated per track rate scale.

IE. If you adjusted rates from a pattern rate scale of 1/2x:

  1. Switch all tracks back to 1/2x.
  2. Switch back to per pattern rate scale.
  3. Switch from a global rate scale of 1/2x to a global rate scale of 1x.
  4. Switch to per track rate scale.
  5. Adjust the rates back to the desired rates.

Perhaps there is a more elegant way of doing this, but I haven’t found one.

1 Like
#122

Had this happen tonight while jamming away, hard boot needed. Latest FW.
Anyone else run in to this one?

IMG20200220233248
IMG202002202332483456×4608 1.24 MB

#123

A few people:
https://www.elektronauts.com/search?q=exception%20error%20%23elektron-gear%3Adigitakt

Best to report it to Elektron.

1 Like
#124

looks kinda cool tbh did it corrupt anything ?

#125

Not that I know of… haven’t gone through old projects or anything

#126

Hi, did you ever hear back from support about this?

Delay, Reverb & Comp values won’t return to saved state when pressing
Func+Delay/Reverb/Master+No (despite the screen telling you it has)

#127

Hi Neil,

Thanks for the report! I have reported that mixer page should not state Randomize or Reload Page Mix to our developers. We are already aware of the second issue that you report and are working on fixing it.

Regarding not being able to randomize per trig, this is not supposed to be possible.

Regards,

Patrik - Elektron

On Sun, 30 Jun at 11:52 AM , Neil <neil@runbox.com> wrote:

I have installed 1.11 and looks great apart from the following items that appear to be bugs.

Randomise

  • Mixer states randomise message when pressing Page + [YES] but do not randomise

  • Compressor and effects Delay, Reverb pages will randomise but won’t reset / reload with Page + [NO]. Message states reload but changes do not revert

  • Trig cannot be randomised. There is no messages here so i presume this is by design.

2 Likes
#128

Ok Cheers :+1:

1 Like
#129

This bug seems to have persisted since the DT first came out (I’m on 1.11 atm)

Am I crazy, doing something wrong, or just missing something? Is chromatic mode just janky? I feel like Elektron should really be better than this…

What a buzz kill to have a machine that can record, copy/paste, nudge notes, reassign tracks (all without pressing STOP) until… oh, every note recorded is at 128 steps… :man_facepalming:

Hanging notes?
#130

The above refers to the “note length bug.” Considering the thread was relocated here, I’m assuming the answer is a resounding YES! :roll_eyes:

#131

Could you elaborate on this?

1 Like
#132

Sure. When recording in chomatic mode the note hold length often glitches to either ridiculously short or long (far from what was actually input). You then have to manually change the note lengths.

In practice, 1. you’re recording, then in playback 2. notes either hang (glitch long) or basically disappear (glitch short).

#133

Anyone else still getting weird prog. change behaviour - as above? I’m getting this with my DT>DN. Not behaving properly at all.

1 Like