Digitone II bug reports

I found an “issue” with arps triggered by swung steps, if you trigger an arp on a swung step it will start swung and remain offset until the arp stops playing. I don’t think it’s a bug, but I think it’s problematic and annoying to workaround. Really makes me want a way to disable swing per track.

Some of my thoughts on the topic:

(very bad video quality sorry)

Metronome Preroll doesn’t work if Transport Send is enabled.

Also live recording doesn’t always capture notes correctly. In particular, when playing stippled longer chords, note lengths aren’t reliably recorded and frequently get shortened.

3 Likes

The arp sync drift that prompted me to make the post seemed to be happening predominately when live tweaking the comb filter frequency. But I do have a small amount of swing on the pattern.
Of course, since willy-nilly changing machine parameters I am now not seeing the problem. Murphy’s law.
Will try to be more attentive next time. The joys of early adopting complexly engineered products lol.
I have 100% faith in Elektron to squash as many of the little bugs as soon as they possibly can.

well comb filter being a delay controlled by the filter frequency, perhaps the delay effect introduced by the comb filter is throwing off the sense of arp timing?

But if you triggered the arp on a swung step I think that could explain it.

Not sure if track layering is intended to work on midi tracks. If it is, it does not work.

1 Like

That’s a shame, seems like it would be really useful to be able to trigger midi tracks from audio tracks and vise versa.

Unquantized live recording (with external sync) using both external midi and internal key input is weirdly off, regardless of how precisely I am playing when recording.
This is especially apparent when I am trying to record polyphonic sequences. No matter how precisely I play, some notes/steps of the recorded sequence end up being extremely short, or extremely long, seemingly at random.

The recorded sequence sounds nothing like what I played. Sometimes though, the recording is quite precise. I encountered similar issues on other Digi’s previously, but am no longer encountering it. This makes me think this is a bug and hope it will soon be fixed!

Edit: Rebooting seems to solve the issue, for the time being.

6 Likes

Hi,

What do you think, how reliable is DN ii as an audio interface? I have now used it with my new M3 Mac Book Air (Sequoia 15.0.1) and have had couple of sudden dropouts which need rebooting of DN ii. I remember well I gave out with DN (1) for same reason. It was not reliable like a good quality audio interface. On a gig you cannot tolerate even a slight possibility of audio going out suddenly.

So i’ve been having this issue where if I manually input in a chord using note edit I’ll get weird voice stealing and transpose issues with that step when the sequencer is running. I could start and stop the sequence fast and it would almost cycle through these notes / transpositions like it was running on an arp or LFO… but nothing was applied. I tried everything but nothing would fix this behavior until I manually played in the chord in live record. Now it works perfectly. Weird.

I’ve seen this several times when connected via USB audio to iPad.
Rather that rebooting DN2, etc. just try unplugging and replugging USB cable. That seems to force something to reset and audio returns.

Voice stealing issue?

I’ve noticed this before but wasn’t sure what was happening.
It’s mostly noticeable with a new pattern.
When adding a track and more voices are getting used , the sound of the tracks that are already playing changes.
Allocating voices to a (muted)track changes the behavior of other tracks.

In the video it’s most noticeable on the arp.
In the beginning of the video I unmute track 7(shortly) and the arp on track 8 changes. Then I start allocating voices to track 7 while it’s muted and when the available voices decrease the sound on track 8 changes(a lot).

https://www.dropbox.com/scl/fi/p9y1knns976fjvm40d95z/DN2-voice-stealing-issue
Anyone else noticing the same behavior?

I’ve been syncing Digitone 2 to Digitakt 2 (DT2 as master clock) and vice versa. And I’m noticing drift in the delay (pitch shifting) on the device I’m syncing. Not on the one using the internal clock. It’s not the case when I sync the DN2 or DT2 from another device (i.e. a midi controller or daw).

FWIW, I get the same pitch ‘nudges’ in the DT2’s Delay as the clock sync drifts too, so it’s not just a DN2 issue.

Same.

Anyone else noticed an issue with their Digitone II turning itself off and instantly back on? Not sure if this is a power supply problem or something else.

Secondly, I can’t raise a ticket online because I can’t make an Elektron account because the ‘create a new account’ link doesn’t exist. I thought this was just an issue on mobile, but I cannot even access it on Desktop. Is this an issue for others as well?

Not sure if this is intentional but the body hold and decay on FM Drum only affect the output of the Carrier and not B1 and B2 in algos 5-7.

Why is the noise CHAR param inverted for both S+H modes? (max at right as opposed to left)

Also, when both are at maximum, they have lower fidelity than grain mode with the knob all the way to the left

Regarding the bug reports in this thread, @ThomasJ from Elektron gave some directions:

"As always, if you have a very easy way of reproducing it, a clear description, with a setup and step by step instructions (and preferably a project file) with expected and actual results will basically always be prioritized. Suggest exact devices, connections, parameters etc, and things have the chance of being picked up and fixed much faster. This goes for all bugs. We want to fix it all :slightly_smiling_face:

The threads here are mainly for users to share their findings between each other, and then they should submit a ticket to our support. This gives best chance for us to take action."

3 Likes

Man… Got lots of device lock-ups tonight… Like 5 within 1/2 hour…

The only thing I was really doing significantly different than “normal” was playing around with track layering triggering slave track arps.

At least 2 of these lock-ups came while browsing/loading sound presets while seq was running.

There’s not some kind of log file on the device is there to help debug?