Digitone II bug reports

Elektron Gear Digitone/Digitone Keys
42

Assuming this is a bug: when you live record something, then shift the start of the melody to the 1st trig using FUNC + :arrow_left: in GRID mode, the first note will not trigger a note upon pressing PLAY on the first run if the microtiming is anywhere left of center (ON GRID), even if quantization is set to 100%.

I can reproduce this every time.

1 Like
43

This one is harder to describe and difficult to replicate on init patches, but there are a few parameters I have found in WaveTone, that under certain configurations produce very rough contrasts and pops when parameter values change by 1 value. They all seem to occur with the second oscillator and when values are at extreme ends.

  • When using a PRIM table, WAV2 waveform set to right end (square), value: 120, audible pop when going to 119, not as smooth as 119 to 118.

  • When OSC2 level is set to left end, value: 0, audible pop when going to 1.

  • When TUN2 is set to right end, (+5 octaves), value: 60.00, audible pop when going to 59.99.

1 Like
44

I’ve had 4 freezes on my DN2 so far. Sound stops, the whole system freezes and I have to do a power cycle. Recent changes are lost. Anyone else experiencing this?

2 Likes
45
  1. Trig mode: sound pool (the default one available)
  2. record something via the DN2 trigs
  3. turn on arp (func + arpeggiator)
    = the sound gets weird
    it also works with the arp on at the beginning and then turning it off: it will half reset the sound.

46

Yes I had this. I tried to identify the culprit without success, yet.

47

Same, I do not see a common pattern when it happens, so I have no idea what could cause it.

48

Digitone II bug reports - #28 by sezare56

49

This is happening to me, too. I can’t replicate it reliably. Happens usually on a fresh pattern on a new project.

2 Likes
50

Has anyone had any issues with LFO speeds? I can’t seem to get a really slow LFO sine or saw wave. Even if I set the multiplier to 1 and set SPD barely above zero it still oscillates more than twice per bar.

Edit: to test it i tried to modulate pitch with a square wave. Several oscillations per bar at above setting.

51

Isn’t this just how these machines work? I’ve always found it best to nudge the step back to the right of centre.

1 Like
52

This is the case on all Elektrons devices, not a bug as far as I know. It’s before the start of the pattern so it only plays on the second.

1 Like
53

Yes, I’ve had this happen (though sound didn’t stop), it froze the current sound, and audio input continued as normal. In all cases when it happened to me it was due to editing a trig on an arp preset via an external midi keyboard while the sequence was playing.

54

Works for me. Try again with an init patch…

56

did create a ticket for this one (as for the previous one)

  1. create new project
  2. load a kit into the sound pool (say, acoustic)
  3. all the presets are called untitled0~16 and are the default sine wave
  4. load a kit to the pattern (say, solid): kit’s presets loaded fine on the tracks (nothing new in the sound pool though)
  5. load the acoustic kit again in the sound pool: untitled0~16 are still there but now you have the solid kit presets after that (not the acoustic one though)
57

I wanted to try track layering from track 1 using Euclidean, to track 9. The key for track 9 does illuminate at the same time, but no track 9 sound is audible.

Is that expected with Euclidean, or a bug?
The Euclidean trigs are not locked.

1 Like
58

Actually, when I locked the Euclidean trigs, then went back to Euclidean mode, track 9’s audio output did start.

1 Like
59

I guess it also work if you place trigs on the first steps before using Euclidean…

60

I’m having the same issue but with Octatrack MKII as master clock. I also swapped OG DN for DN2 and didn’t have the tempo jumping with the OG DN.

EDIT: adding the issue since Robert’s original post is so far up. The tempo seems to search which makes for jumps and detuned wobbles in the delay signal (same for delay added to chorus) and not in a cool way.

I’ve searched through every setting I can find to see if there’s something that’s effecting it but haven’t found anything that solves it.

1 Like
61

I just read in the manual this is intended. I agree it should be excluded.

62

I noticed when p-locking retrig on, then clearing that trigs locks, the retrig still occurs. highlighting the trig you can see it is still p-locked.