Not sure of what I did.
Maid a pattern, made a 2nd one with different settings, went back to the first one : previous settings were gone. Maybe I was in perform mode. Its been a WTF moment…RTFM!
Aargh, what a nightmare. The night of the living autosave-zombies. No way out of autosave-hell, once implemented, it seems. IMO one should be able to disable it. ( i know there‘s project reload on elektron but…)
That‘s a minority opinion strangely i know.
Edit: well reading the manual there‘s autosave off possibility on tr8s, that was also part of my elektron feature request i remember. But still possible to mess up by forgetting pattern is linked to another kit or something it seems…
2 Likes
After a few hours with the DT2 I’m still baffled by Kits. I was hoping they wouldn’t be a Dark Art, like parts are on the OT, but scrolling through this thread I get conflicting info and just come away more confused.
All I really want is decoupling of the pattern/trig from the sounds, i.e. data the pattern to shared or common sound configuration (sample+other params)
1 Like
Yeah autosave can be a blessing (for those, that forget to save stuff) or a curse (for those, that forget to reload or undo unwanted changes). I’m not particularly fond of it either and would prefer to disable it.
3 Likes
4 Likes
Yeah this made a lot more sense to me. Thanks.
Not what I hoped coming from AR, but still cool nonetheless.
I don’t have my DT2 yet. What happens when you hold kit perf button and record (copy) ?
It might be a great feature request to have that actually copy your current kit so you can paste it to other patterns, if this combo currently doesn’t do anything.
This would make it very very quick to update your core settings if you just go back and fine tune the mix a bit and need the change to reflect everywhere.
This is really my main use case for kits. I’ll iterate on a mix and it’s a LOT of copy pasting on the old digis to sync changes across patterns.
Additionally, I’m really curious: you can save your kits to pattern without having to literally save them to +drive correct? It would be pretty annoying to have all of those random / one off pattern kits taking up the same space I’d use for a more cultivated “kit” I planned to re use.
2 Likes
I just realized something super annoying with DT2 Kits : once you saved a kit, there is no way, from the pattern, to find out what kit was saved from this place. So let’s say you get back to a pattern after some time, modify its sounds and want to save the kit over the “original” one, you can’t. The best way I can think of is to take the habit to save the kit’s name in the pattern’s name.
4 Likes
What happens if you load a (preset) kit onto a pattern, but do not do “Save kit” (on the pattern)?
Changes you make to any of the sounds on that pattern will still apply on that pattern, right? What if you switch patterns/projects and come back to that pattern? Will the changes you made (from the original preset kit) still reflect? Or do you have to save the kit on that pattern for changes you make to sounds to become permanent on that pattern?
Once you’ve loaded a kit, it becomes exclusively a part of the pattern. So if you change the presets, it won’t affect the kit, and if you change the kit, it won’t affect the pattern.
1 Like
5 Likes
Thanks, clearly there’s something I’m still missing. I’m off to read the manual first. 
fml 
1 Like
To answer my original question regarding “Save the kit as TEST.” - I misunderstood that statement as meaning you are saving the kit as part of project/pattern.
I understand now that you can only save kits to the ‘global’ Kits location on the +Drive.
So
- Kits (on the +Drive) are global and independent of projects
- You can import a Kit from the +Drive into a pattern
- that pattern now has a copy of that Kit , i.e. it is a convenient way to initialise all 16 tracks with preset sounds or midi config
- any changes you make to sounds or midi config (i.e. track parameters) in the active pattern does not affect the original Kit on the +Drive
- but you can choose to (at some point after tweaking
sounds/midi config) take all the track parameters of your active pattern and save (export) them as a Kit on the +Drive, which you can then import into any pattern in any project in the future - every pattern in a project has their own separate set of presets, that could have been initialised from some Kit (on the +Drive) or started from scratch. Changes you make to track parameters in one pattern (i.e. the “pattern’s kit”), does not affect the corresponding track(s) on other patterns in that project. If you tweak a bunch of sounds in one pattern, and want to apply it to the other patterns, you can export the set of sounds and midi config to a Kit on the +Drive, and then load (import) that Kit on the other patterns (or maybe there is a shortcut to copy/paste this directly between patterns without saving as a Kit to +Drive first)
I hope that is correct.
6 Likes
We’re going to need Merlin’s guide to the Digitakt II
2 Likes
To me, everything you state is correct, except maybe this sentence that I don’t quite understand :
I would say :
" every pattern in a project has their own separate set of presets, that could have been initialised from some kit or started from scratch".
2 Likes
lol, wording conventions have always been elektrons main issue. trigless triggety trig 
3 Likes
Yes.
If you save your project, it will save the kits as your pattern’s kit.
If you don’t, or if you reload your pattern, you come back to the state before you loaded the new kit.
“set of Presets” < Kit
Kit = “the set of Presets of all the tracks + some settings such as CTRL-SEL and compressor, FX and such”.
4 Likes
I said “separate kit” because the manual talks about the pattern’s kit, but I agree your wording is less prone to causing confusion.
I have updated my wording above to hopefully avoid adding further confusion.
1 Like
Words are hard.
There is an old saying, something like “The two hardest problems in programming is concurrency and naming things”.
2 Likes
Unfortunately this is still (not) possible. And I can understand the confusion as it’s not very clear how kits interact with the other data types (patters, projects, pools, etc).
Kits still work mostly the same as on the DTOG with two additions:
- Kits are now separately saveable / loadable, so it’s easier now to load a complete kit in another pattern.
- Kits have a PERFORM KIT mode so the current active kit will be temporary applied to all patterns you change to when enabled (a global kit).
Kits however, always remain to be a part of the pattern it was loaded to, just like the DTOG.
If you want a kit, which is enabled during PERFORM KIT mode, to be permanent applied to a different pattern the only way now is save the kit and load it manually from the kit menu in the target pattern.
The possibility to apply (commit) the current kit which is active in PERFORM KIT mode more quickly to a pattern would be a nice feature request. Or a way to copy kit data from a pattern and paste it in another pattern (without the reload sequence data workaround).
2 Likes