Digitakt 1.04 : Bug reports

Elektron Gear Digitakt
#46

I have submitted a report ticket for this, can any body reproduce?

  • When adjusting more than one CC knob at a time, one of the knobs stops sending real-time CC values until power cycling the device.

Locked CCs still will fire, as will the “default” full set of CCs when there are trigs in the sequencer. Loading a new pattern or project does not remedy the situation, only power cycling the device.

Exact minimal repro steps:

  • Create a new project
  • Go to track MIDI A
  • Go to SRC page
  • Unlock and set CHAN to 1
  • Go to FLTR page
  • Unlock the first two knobs
  • Drop a trig or trig-less lock on the sequencer and hit play then stop, or simply manually trigger the track at least once (1)
  • Power cycle the device and wait for it to boot back up
  • Twist CCs knobs ONE AT A TIME. Notice this works as expected.
  • Twist at least TWO CC knobs at a time. Notice that one of them will immediately stop sending CC values.
  • This process can be repeated with any combo of knobs, the end result is only a single knob will be working as expected.
  • Power cycle the device and wait for it to boot back up
  • Notice that knobs again work as expected (so long as they are not being twisted at the same time)
4 Likes
#47

This has already been confirmed and reported.

8 Likes
#48

Tried some more advanced midi stuff today, 2x complete crashes and one boot that froze. Turned it off for a few hours and then tried booting again and it worked.

#49

Stability has been better for me since 3.04, but I’m still getting freezes when using MIDI in (keyboard) and out. Sometimes the sounds will play direct from the trigger but stop playing from the sequencer, and sometimes complete freezes. Recording into the sequence from external MIDI keyboard seems to cause it most often, even though it sometimes works as it should.

#50

nice catch, but what a PITA. :frowning:

#51

Ok, everything I thought was a bug, is not. BUT updating threw my stuff out of wack that I had to manually restore it all, like the patterns setted to 10/16 instead of 16/16 like I originally had them. Little things, easy fixes on user end, but will mess up your day.

#52

Get freeze and have no control except the volume level when using keystep to send random arp signal to digitakt, which controls 0-coast and has some trigs at the midi track. It usually happens when I try to stop or pause the arp.

1 Like
#53

Might be user error, but I think I noticed someone else post this too: on the trig page, FLT.T doesn’t seem to work. It never retriggers the filter envelope.

Edit: I mean on lock trigs (Triggless trigs)

Edit: hmm it does work. No idea why it didn’t at one point, but pretty sure it was my own fault :stuck_out_tongue:

#54

I get this too, i think It’s just receiving MIDI in general and then either Receiving a stop message or pressing stop on the device.
Also, still having crashes when playing a MIDI track with external input or pressing trigs in chromatic mode whilst the sequencer is stopped. It freezes when you press play after haivng the sequencer stopped for a while, doesn’t happen every time but still pretty annoying.

EDIT: Receiving NOT SENDING

#55

Same here. Usually have to press knobs 2-3 times to enable MIDI functions.

#56

Problems with enabling MIDI functions (button press) as well. really prevents a good workflow,
the same with changing small values. when turned too slow the value doesn´t change, when i turn
it a little little bit faster… it changes 2-3 values. hope both of these things get fixed soon.

Had a new bug today. Midi-information (sequenced stuff, not the clock) was sent out after having stopped
the sequencer. I mutet all midi channels… changed to an empty pattern, switched the unit off and on…
nothing helped. after changing the midi-channels several times… it worked again (nothing plugged into
midi in or usb!)

Already sent to elektron: Automation resets the note values, which is supposed to be normal as answered.
It definitely feels like a bug. Hope this strange bug-“like” behaviour will be changed.

#57

Not sure if this is a bug or user error … I play a a note on the first trig that runs the full 64 step length. Now I have a note looping every 64 steps. when I live record the p-lock to change the pitch slowly down over the course of the 64 steps, when it gets back to step 1, the note now cuts off after 1 step. when i go into grid record mode, I can see my first trig in red and the rest of the trigless locks in yellow, but all I hear is that one first step of the note. What am I missing? Is pitch not p-lockable?

#58

One of my folders that should be full of samples has nothing in it if I go into the folder I can’t back out and I can’t delete the folder because it has samples in it… at a loss on how to fix it. any ideas?

1 Like
#59

Don’t know if it is already mentioned:
Tracks remain silent if I press play until I press a trigger button…
I have to do this for each track until all 8 sample tracks play…
This one is new for me and might be solved when I restart the DT but it is annoying…
Yes, I am on 1.0.4 :slight_smile:

#60

Same thing happens to me although it just seems like any large amount of midi data thrown at it while it’s playing back more than one midi track out seems to overload it. I’ve had it lock up both during live recording and just playback. Note hangs etc. Nothing responsive have to reboot and then it’s fine for a while.

#61

Probably has been mentioned, but Mute Mode exits when I change patterns. Not all the time, usually when I’m slower with the button presses.

#62

If I have one MIDI instrument configured on MIDI track A, then I have the same instrument set up on MIDI track B, but with a different program (preset), there is an issue when switching between the two voices. For example, I have MIDI track A playing in Pattern 1, and MIDI track B playing in Pattern 2. When I switch to pattern two, the first time B is triggered it does not fire. The following triggers for MIDI track B then act as expected.

I am also getting a significant amount of freezing (on average about once every 2 hours or so). The UI will freeze while the audio continues to play, requiring a restart. I haven’t noticed any pattern to this behavior other than the fact that it usually happens when I am utilizing MIDI sequencing (I have been using between 1-4 MIDI tracks most of the time.

Luckily after restart, it seems all my settings have been preserved so it’s not a huge inconvenience, but would obviously be terrible in a live setting…

#63

I don’ think that it was a bug - the first note on the second track indicates a programm change.

#64

me too

#65

So the first note triggered on a MIDI track with a new program will act as a program change only and not send note data?