Wait, so I could load Kit 4 on patterns 1-6
Adjust kit 4 on any of these patterns, and have it reflect on any other pattern with that kit loaded? That’s all I can really ask for.
Wait, so I could load Kit 4 on patterns 1-6
Adjust kit 4 on any of these patterns, and have it reflect on any other pattern with that kit loaded? That’s all I can really ask for.
No. Unfortunately.
You can load and save kits the way you load and save Presets.
Once it’s loaded, the link to the saved version is gone, so loaded kits are independent.l one from another.
For now at least.
Oh ok. So if I understand correctly:
I can adjust a kit I want to use on a couple of of patterns, and just make sure to load that kit again on those other patterns.
Still beats copy pasting parameter pages across multiple tracks heh.
You adjust your Kit on a pattern, save it as a new kit (or overwrite the previous one) then switch to your other patterns, load this kit.
Then save your pattern, or project.
It seems a good solution to me.
You can use kits or totally ignore them.
I think it’s a win!
I am not impressed at all by the Kits!
I thought it would be like on the AR or TR8S.
It’s very slow to load kits and even patterns need some time to load after pattern change so the DT2 is not suitable for live performance atm.
Is there a trick behind it or am I doing something wrong?
I received my unit 30 minutes ago and tested kits right away.
My observations so far (caution, I’m might be wrong on some points):
when you load a Kit, it checks all the samples, and adds them (if not already present) in the RAM by giving them the first empty slot available. This might indeed take a few seconds depending, I guess, on the size of the samples.
After that, loading a Kit that has already been loaded before is quite fast.
The RAM state keeps unchanged after power off, so that’s great because kits that you previously loaded are still fast to access. (Once the project is “fully” loaded, which is quite long).
Assumption : since there are 1016 samples slots in the RAM, that should allow to “preload” 63 kits of 16 samples (assuming that all kits are fully different of the others in terms of samples).
To test : what happens when the RAM is full and you try to load a new kit ??
Thanks for the Tip. Even if the samples are in the RAM and if you change the pattern where another kit is loaded it needs some time to fully adjust all settings. I use bigger sample chains for drum s. And it really needs a lot longer to start up even with few samples loaded. My OG need like 5-10 seconds even with 60-80 bigger samples in the RAM
Well, bad news (although sort of what I expected). If your RAM is full and you try to load a (previously not loaded) kit, you get :
How many would you need ?
Can’t the 128? Preset Pool sounds be add ?
Need to test it, but I would be surprised.
I would virtually need an infinity of kits. That’s all speculative as I’m chasing an old chimera that would be a hardware machine to be used as a sound module in which I could create drumkits and just keep adding them during the years.
I’m super happy with Ableton Drum Racks (that are in a way even more powerful) but I dream of a dedicated hardware for holding drum sounds (not a controller, but reconsider it after all…).
For live purpose, I guess you don’t need more than 63 kits ?
Where is the limitation if you can create many kits and previously load them in several projects ?
The limitation is file management.
I will have lots of “unused” kits due to unfinished songs, songs that I don’t play anymore but want to keep available.
If there was a good file manager that would allow to save projects on a computer and then drag’n’drop kits from different projects to another project, then i could easily make an up-to-date project containing the material that I need to perform live, and i would be just happy.
Off-topic :
On a larger scale, that’s the problem I always had with Elektrons (and hardware in general) and that prevents me to really use them live in a long term : project management.
I have roughly 60 songs that I might perform live, plus hundreds, if not thousands of unfinished tracks that I might revisit someday. That’s how I work, I often go back to old stuff, and suddenly know what to make with it after years.
That’s what I love the computer so much : virtually infinite memory and an open folder structure, easily readable and enabling copy+paste of tracks/sets/presets.
On Elektron machines, I always feel limited with space and organization pretty quickly, and it prevents me from doing long-term projects with them.
I am so glad it’s not like TR-8s. To me it’s the most annoying thing on that machine - I was constantly screwing my patterns because I changed some sound or setting on a different pattern using same kit. It’s actually part of the reason why DT replaced it in my main setup.
What is the process of reloading a kit, once it has been changes from somewhere else? Is there some shortcut or is it like loading it for the first time, which (I guess) means first locating it among all the saved kits in loading it again?
It’s about changing kits on the fly ! As I play techno and most patterns are quite the same I just like to exchange the sounds in real time without screwing up my patterns. On AR it works great on the DT2 kind of 
This morning I lost a pattern settings by modifying the kit in another pattern. I guess I should do a tabula rasa with a kit per pattern to avoid mistakes, and assign kits when necessary, as on A4, AR…
Flu/headache doesn’t help to make this clear today…
Any thought about this ?
(@LyingDalai…)
I tried to make it clear here:
Sorry a bit off topic, I don‘t have tr8s. ( only tr-8) I feel kit-confused again, sorry.
Some years ago i was argueing ( and sending a feature request to elektron), big advantage of tr-8s above elektron analogs ( from reading the manual) is the possibility to write-protect a pattern for less mind confusion, possibility to go back to that pattern as once saved (without project reload as on elektrons, or reload from project on digis. On (now old) digis its less confusing, but I loose nice possibilities with kits) .
With the same kit assigned somewhere its still possible to mess up the pattern so that its not as saved and write protected, when you go back?
According to me, this is not possible.
As soon as you load a kit, it’s no longer treated as a kit, but it’s copied to the pattern locally. So it should be impossible to modify a kit other than explicitly saving it to its original location.
You mean pattern lock function? As far as I’m aware, this only means pattern changes aren’t automatically saved, but changes to the kit still affect it in all patterns to which that kit is assigned.