The Digitakt Feature Request Thread

one sample for each step

1 Like

Itā€™s only one sample per step, but you can set an LFO to sample slots and based on your settings it will swap samples per step almost at random. Itā€™s a monophonic sampler so it is not possible to have multiple sounds on one step without resampling.

1 Like

Awesome. This machine just keeps getting better! Thanks guys!

Hi Elektron team .

1 There is no sample playback when removing samples from the samples list 0 to 127 .
Func / Yes does not work here.

Also Func / Yes is realy crappy idea. why not use the keyboard notes simply . holding func seems very stupid to do basic things.

2:
Would like to see , Pattern retrig Play re-start any ptterrn of 1 step by 16th notes , currently min value is CH.LEN = 2 that is not flexible to do live the way its setup and restricted.

also while sellecting pattern from same button , this action does not retrig start playing step one.
You can go from pattern 1 to 2 and 2 to 1 , but CH.LEN is too long to retrig the kick etc , and its not nice to do. it feel clumsey as is and dum move.

Changing this to pattern retrig on , and CH.LEN = 1 or 16th note .
this would enable live playing and retrig of first beat of a bar , al la RS7000 , QY700

does yamaha own the idea of this? like we had this idea over a decade ago.

Please fix .

also switching banks and patterns holding a Func button maybe okey , but we also NEED A FULL MODE FOR THIS that is latched on off . not timed out ā€¦

3 In Track mute for global mutes , there are to many lights flashing on off . i just want to see what is muted onlyā€¦ not the notes being played. Have to litrally press stop and toggle mute modes to see what is muted atm. The lights flashing are to dazzling too. To bright.

TY .
:slight_smile:

1 Like

I agree Fn+Yes is awkward for something as fundamental as preview. Personally Iā€™d like the option to auto preview as I scroll through the list

2 Likes

auto play while scroll is good , or at least while holding Func , one button heldā€¦

4 Likes

Track Button lock mode. Where you can change tracks without triggering a sound and without holding track down.

3 Likes

yepp, that paralizing firework while having every trig on every track is a kind of cancer to my eyes!

also experienced that you donā€˜t see the mute states properly while having too many trigs?

thatā€˜s what i thought from the beginning, too bright and too much blinky stuff ā€¦
without additional room light, or in total darkness i feel tired very quick!

thereā€˜s a thread about this!

3 Likes

(Next-trig) microtiming as LFO destination!

3 Likes

Oh, yes please.

If we could work out something similar for pattern chains (ā€œJust play this pattern for a minute while I mess with it, pleaseā€) that would be smashing as well.

8 Likes

Yeah thats a seriously great idea

1 Like

Pattern counter in the display? Would it be nice - Showing how many times your pattern have been played - think it would help me to structure betterā€¦

2 Likes

Hi everyone !
sorry if mistaken but :
if i program a 16 step sequence and iā€™ll set the track lenght to 4 steps, enter Grid Recording Mode, and then shift the track (p-locks) left or right (FUNC + Arrows </>) it will only shifts the 4 steps whitin the 4 step page. Why doesnā€™t the DT shift the 16 step sqnc over the 4 step page (loop). This way we could make nice evolving loops by cycling through the 16 step sequence. That would be cool !

2 Likes

Nice idea.

A different way to achieve something similar? A new trig condition to ā€œrandomly play a single retrig from this stepā€. Then, you could set a 1/80 retrig for the step and get hits that fall on/around that step. To include early hits, microtime the step backwards some. I havenā€™t actually counted but Iā€™m assuming if retrigs go to 1/80, thatā€™s the same resolution we can get via the mico-timing menu.

What do I know but seems that could be easier to implement since conditions are already step based whereas the LFO is param based.

1 Like

ā€œRotate through chordā€ trig type for MIDI tracks would be a really handy, DT-like way to get a lot of variation out of single pattern.

The idea: Record a chord to any step. On playback, instead of playing that step polyphonically, on each loop the DT plays a single note from the chord.

Simple example. Assuming a 4-step pattern with these four trigs:

  1. Chord of C - E - G
  2. Rest __
  3. Single A note
  4. Single F note

Loops of the pattern would trig like:

  1. C __ A F
  2. E __ A F
  3. G __ A F
  4. C __ A F
  5. E __ A F
  6. And so onā€¦

You could use it to vary a note in a bass line or melody. You could use it on several steps to get something like a 8-bar bass line into a single 2-bar pattern.

Ideally, the trig type would have a few variations like

  1. Play chord notes from low to high
  2. Play chord notes high to low
  3. Play notes randomly
  4. Play each note twice (similar to some arpeggiators)
  5. ?

Oh, speaking of arpeggiators, if you were to change the 4-step pattern above to a pattern length of 1-stepā€¦ cough bonus cough.

Would be most ideal if it was a separate type of trig parameter instead of a new type of trig condition so that it could still be used along with the existing trig conditions. But a new trig condition would work!

And, so long as Iā€™m dreaming here, if this could work for MIDI trigs, maybe it could also work for audio trigs one day? They would still be monophonic trigs but you could record chords in to get the same sort of mileage out of a single pattern. If the trig didnā€™t have one of the ā€˜rotate through chordā€™ trig conditions applied, it would choose the lowest note as the trig.

1 Like

Clock divider per track. Miss that badly

11 Likes

SCALE PER TRACK
microtiming update(4mre possibilities):cb:
it will be so nice !

1 Like

WORD.
Fix track scaling.
64 16th notes against 16 whole notes?
That is not too much to ask - the OT does it - it would make these new boxes WAY better.

1 Like

I find the lights confusing, but that might just be a learning thing as Iā€™m only a few weeks into Digitakt ownership.

However, in Grid mode I canā€™t tell the difference between Trigs that have conditions (e.g. to be triggered in a fill) and those that havenā€™t - they are both the same shade & intensity of red.

Perhaps there might be a way of differentiating them via brightness or colour (yea, more colours, why not?)

In grid mode a trig that has a parameter locked to it, for example a trig condition, should blink.

1 Like