Digitakt "Kit" Structure. How is it different?

Can we talk about this whole new Kit scheme?

I see on Pg 30 of the manual that Save Kit and Reload Kit are options.

What about loading one pattern’s kit to another pattern?
Is this possible, or is the only way to do this going to be to use COPY commands for each sound, track by track, from one pattern to another ?

…Long time listener, first time caller, I’ll take my answer off the air…


Wondering about this too… or can you copy a pattern and everything would copy along with it? Then you could just clear the trigs on the copied pattern? There’s an option in the pattern menu to clear only the sequence data in a pattern, keeping the kit intact.

From the manual it looks like you can copy/paste the whole pattern, but not just the kit…

1 Like

That would work for me. Copy pattern, clear sequence data = copy kit (essentially). Takes just as much work as loading a kit on the Rytm and then saving it as a new kit. Less work actually.


figure, something must be in the works… hopefully something menu-less…
imo, just a func+something command to copy/paste kit would suffice.
maybe func+track+copy/paste…?

Copying/pasting/clearing an entire pattern seems to be the only way now, but what if you want to load a different kit into your current pattern? No dice, or copy sound-by-sound (ugh!)


As adamjay suggested a bit back, it would be nice to be able to link one kit to multiple patterns so that changes to it are retained through pattern switching…


Of course you could just copy and paste patterns to get those parameters/kits into other patterns.
However, that is not the issue. Only being able to copy the kit via copy/paste of a pattern excuses the elegant functionality of kits;
Being able to edit sounds, no matter which pattern you are in, and having those parameter edits be applied to other patterns.

Otherwise it has the potential to become a major workflow issue.

Being able to move fluidly between kit editing and pattern (sequence, notation) editing is a cornerstone of the Elektron workflow.

Perhaps I am looking at DT too heavily through the lens of the highly flexible and elegant schemes of the existing Elektron instruments.
But I only blame Elektron for that, because Kits are bloody brilliant, and if they are now hamstringed for simplicity and can’t be linked to 2 patterns or more, then I question the design decision of form over function.

And somehow, with DTs and the manual all out in the wild, info regarding this concern continues to remain scarce.


yea… but, no matter where the kits are stored… wouldn’t we basically end up with the exact same kit concept and its inherent complexity we have on the other machines tho…?

Maybe not if by default there is always a new separate kit per pattern, but there was an option somewhere to link pattern to an existing kit… And of course just being able to load one would be nice…


aye… and the kit is only saved if you save the pattern which owns that kit? could work…

Save kit, and reload saved kit are available functions.

But load Kit is not. Load kit is not the same as reload kit.

And I crave more information about the consequences of such an omission.

We have been told the Kit implementation is different.
But is it different, with Kit linking?
Or is it just a fractional implementation of what we are accustomed to?

There is “simplified” and then there is “reduced”.

I am not here to criticize or complain,. I am here to understand.


I have a feeling we’ll see some improvements on this but I’ve been hesitant to say anything because this thread is so sensitive :smile_cat: I don’t want others to start complaining about some missing thing I suggest, or hoping it will come because I said something and possibly be let down… :sweat_smile:


I wanna know this, too. Crippling the kit system just because they couldn’t figure out a more streamlined way to do it, is the easy way out, and most certainly the wrong one.

1 Like

the omission of this is a bit mind boggling to me… i definitely wouldnt be able to use this machine without that feature…

i wonder if its going to come in an update or something

1 Like

After watching the new Dataline DT jam video (https://www.youtube.com/watch?v=l3Iex-NJoEI) where he goes through a few tracks, all one pattern each… I can see that the best way to use it is to just jam with mutes, trig conditions, fills, and as much as you can fit into a single pattern.
Or at least get your sounds really dialed in before copying and pasting multiple patterns, because editing sound parameters will have to be pattern by pattern in the absence of Kit Load.

This single pattern workflow isn’t worse, just different. And is improved by having unique BPM and assigned and saved to each pattern.


Yeah. And I have to go with the “not worse, just different” train of thought. I’d be too caught up in what could have been, with a lot of instruments if I’d focus on how they don’t do certain things.

I haven’t played with the Digitakt long enough to encounter the “I wanna go back and polish all my sounds”-problem. But I could see how that could happen.

But I’ve started a pattern (including sound design) and then copied that to a new one when I wanna evolve. And continued the alterations from there,

The advantage of having everything contained in and connected to the pattern is a plus for me. And now that you’ve raised the question - I think alternative workflows pushes creative output.

I choose to see it as all good!

(Ping @klerc)


For a straight up “pop song” spanning over a number of patterns, I can see the kit per pattern being somewhat challenging. For a more “active” playing style, where you constantly change things and mess it up on the fly, I think it’s a good thing. And the quick save and reload is super fun part of the performance tool set.
I honk where the Digitakt thrives is when operated with dedication and focus. As a playback machine I think currently other machines might be better suited.


I honk for autocorrect :laughing::laughing:


I kind of hope something is in the works here. And agreed we have (in Digitakt) a great instrument to jam on, mess up sounds and patterns, edit patterns and apply mutes on the fly etc etc etc etc.

I think personally I would be satisfied with the ability to load the sound parameters (or kit) associated with one pattern into another pattern. This is effectively a ‘copy and paste kit’ function (as long as the user is happy to save the source kit in its associated pattern).

Of course for full pop productions, with drums that remain relatively static despite variations in the patterns, we have a lot of DAW based options. :smiley:


1 Like

You can save a sound and load into other patterns right?
So when you copy a pattern to copy the kit for a different sequence and you change/tweak a sound in the first pattern, just save and load into the other patterns if needed. It’s maybe a 1 minute job tops.

It can be done, so a kit save/load is just convenient. It’s not a must have at all :slight_smile: