Digitakt II Feature Requests

ripsaw · July 9, 2025, 2:09pm

After writing up the following bug report:

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

I was told that, in fact this behavior is intentional.

Even though the manual states:

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.

I have been assured that this is not a bug:

Because of that, I’d like to put in a feature request to make the behavior consistent with that listed in the manual:

For all current and future uses of FUNC to snap values (on any parameter) maintain that functionality when holding a Trig in GRID REC to create/edit a note trig/lock trig.