Digitakt II: bug reports

[ripsaw]

That’s a problem I’ve not (yet) had to deal with.

I will say that if the Midi-Ox macro workaround listed in that thread (on program change send a stop signal, send the program change, send the start signal) or any of the other ‘set up a macro on an external box’ is as tight as song mode on the most heavy tracks and the micro controller can keep up. If that is the case then I question why having a toggle to perform the exact same actions in the box on program change should take longer/be unfeasible.

There are many ifs there and I’m sure Elektron want a solution that works as close to 100% of the time as possible e.g. sequences running at 300BPM at 2x speed with retrigs and moving between patterns on program change is still seamless as song mode without hitches.

Though It could be argued that giving people the option of such if it makes performing with other gear easier.

Edit. Thinking about it it’s all about the length of the error the user wants to tolerate. A few MS at the start of a pattern during a switch vs timing being out by an entire bar.

[ripsaw]

Bug the expected result when using FUNC + Note on the TRIG page is to move 1 Octave irrespective of if currently editing a note trig/lock trig or not.

TRIG page without trig held:
FUNC + Note (Data Entry A) = Skip Octave ← Expected result

TRIG page with a trig held:
FUNC + Note (Data Entry A) = move one note at a time ← Actual result

TRIG page with a trig + TRK held:
FUNC + Note (Data Entry A) = move one note at a time ← Actual result

TRIG page with a trig + PAGE held:
FUNC + Note (Data Entry A) = move one note at a time ← Actual result

EDIT

The exact same issue is mirrored on the SRC page for Machines that have a Tune parameter.

SRC page without trig held:
FUNC + Tune (Data Entry A) = Skip 12 semitones ← Expected result

SRC page with a trig held:
FUNC + Tune (Data Entry A) = move fractions of a semitone ← Actual result

SRC page with a trig + TRK held:
FUNC + Tune (Data Entry A) = move fractions of a semitone ← Actual result

SRC page with a trig + PAGE held:
FUNC + Tune (Data Entry A) = move fractions of a semitone ← Actual result

[LyingDalai]

@ThomasJ

we are looking into the mentioned issue regarding RevL FwdL

That’s cool

Now if

@ripsaw

The expected behaviour is:

@ripsaw

to cycle between Rev.L and Fwd.L

I think a solution already exists in previous Elektron models, called “PiPo”

[bibenu]

@LyingDalai

I think a solution already exists in previous Elektron models, called “PiPo”

Quite apart from the LFO fix, I would also welcome a ping pong loop (I presume that’s what’s meant here) as a way to simply go to ping pong without needing 2 LFOs as described above.

[ThomasJ]

@bibenu

The ‘pattern change one bar late’ issue.

Maybe @ThomasJ can work his magic here too ?

Unfortunately we haven’t been able to fix this issue yet - but can assure you it is not forgotten.

[ThomasJ]

OS 1.15A for Digitakt II is now released!

[ThomasJ]

@ThomasJ

@kryten42

Any chance of DT1 beta? I reported it 2 years ago when it broke my beloved ping pong

Yes, this will be released in a DT1 update too

For completeness, DT1 OS 1.52A is also out, fixing the modulation issue regarding Play Mode.

[moving_particles]

hi Thomas

is ping pong on the cards for the future for DTII?

with the new slice mode, it seems like this especially would benefit from ping pong looping.

asking for my ambi pads.

[ripsaw]

@ThomasJ Just making sure the above bug report does not get lost in the shuffle of people making feature requests for ping pong playback in the bug report thread.

[ThomasJ]

@ripsaw

Bug the expected result when using FUNC + Note on the TRIG page is to move 1 Octave irrespective of if currently editing a note trig/lock trig or not.

Actually that is not a bug - it works like that on all machines. FUNC for snap values (on any parameter) are not used when holding a Trig in GRID REC. But feel free to submit a feature request

[ripsaw]

Oh, my mistake, I was going off of the manual.

TUNE
Tune sets the pitch of the sample. The knob works in a bipolar fashion, and a value of 0 leaves the pitch unchanged. The range is +/- 5 octaves. Press and hold [FUNC], and then turn the DATA ENTRY knob to snap parameter values to full octaves. Press and turn the DATA ENTRY knob to snap parameter values to semitones.

and pressing and turning still snaps to semitones when setting a trig.

Edit: Feature request made Digitakt II Feature Requests - #1678 by ripsaw

[Hawk]

Really wonderful to see the DTII being so strongly supported, many thanks to the programmers and support staff at Elektron!

I have some great ideas for refinements in the slice machine that I’ll submit!

[Black_Materia]

i think there’s a bug in the compressor routing page.

I wanted to have a pumping sidechain listening to the kick and snare, but when i set the sidechain source to ‘not’ comp, it listens to the full mix as sidechain input, so every channel, regardless of whether it is in the compressor mix or not.

In the case 'not’comp, i was expecting the sidechain source to be all the tracks not being routed to the compressor, and not the ones that are sent to it.

Is this a choice or a bug? both have uses, but ideally in the next update, the options would be ‘comp’, ‘not comp’, mix, and then track1, track2, etc.

[astricii]

I think that’s a bug I can’t replicate that on DN2

[kokosnuss]

Found answer to my own question, midi controller was doing this every time i connect Dt2 via OB to my pc.
I just needed to turn off program changes in midi settings on dt2, and all is good now. For people who might experience the same.
So not a bug

[yeahsometimes]

Is anyone having an issue with USB audio going out to an iPhone from digitakt ii? I had no issues using usb audio from the digitakt in my videos before but can’t seem to get it working post update.

[Watto]

Bug: Triggering slices from midi not working properly.

the above is from pg26 of the manual.

Slices do trigger by midi notes C1 and up (ie, C1 trigs slice 1, C#1 triggers slice 2 etc) but triggering a different slice from the previously triggered slice takes an additional note on/off event than it should.

Example: C1=Sl1, D1=Sl1, D1=Sl3, C1=Sl3, C1=Sl1

I’m on FW version 1.15A

Same outcome with midi over OB, midi over usb(without OB), direct DIN connection.
Same outcome triggering with Arturia keystep and Launchpad Pro MK3.

Edit: made a support ticket.

[lwpweb]

Comb Filter Stays Active on Digitakt II Despite Deactivation and Sample Change

Device: Elektron Digitakt II (latest OS version)

Feature: Comb Filter (newly introduced)

Issue:

When using the Comb Filter on a track (e.g., Track 7), the filter effect remains audible even though:

• the filter type is set to “OFF” or “One-Shot” in the menu,
• the sample on the track has been replaced with a new one,
• all parameter locks (P-Locks) on the steps have been cleared,
• all filter parameters (resonance, frequency, etc.) have been manually reset to neutral values.

The Comb Filter effect still colors the new sample’s sound, despite the display showing the filter as disabled.

Impact:

• The filter effect cannot be fully turned off.
• The track’s sound continues to be affected by the Comb Filter character.
• Standard workarounds such as resetting parameters, clearing P-Locks, or initializing the track do not permanently fix the issue.
• The only reliable workaround is saving the kit and starting a new project.

[sdkboi]

Bug: copy track does not copy retrig page

Issue

Retrig settings (trig page 2) are not carried over when copy/pasting a track

Reproduction

On firmware version 1.15A, copy / paste a track that has custom retrig settings (trig page 2). Observe that the destination track’s retrig settings are different to that of the source track’s.

Expected Behavior

Destination track’s retrig page settings equal those of the source track’s