Easiest way to transfer samples to a pattern I am working on?

[etcetc]

Hi folks, just picked up a Digitakt II. Generally liking it a lot, but wish I could bring in samples from my main production computer a lot easier since I use this as a studio production tool more often than not.

I often use Atlas to organize my samples and it classifies samples quite well, and creates kits that generally are mapped out pretty smartly. It would be great if I could bring those samples into a blank pattern or project assigned to all 16 slots without needing to load them in manually one by one.

Is there a way to do something like this at the moment?

[Bignill]

Could ElkHerd be of help?

Elk-herd 3.2 released!

Okay brave Elektronauts… elk-herd 3.3b2 with support for Digitakt II This is a beta release after a ton of work, and while it works in my studio… you should exercise some caution: Back up your project by saving it on the unit, and then after you load it into elk-herd, saving it as a file on your computer. When you send it back to your device, check that it is all there and is correct. Save a copy as another file on your computer at the same time, so if you later find and issue you can send t…

[re5et]

I’m pretty sure you’d need to use transfer to get them on device and then load them into the sample pool on device too. No shortcuts.

Elk herd might just be a slightly different workflow but basically the same thing.

You could shorten it by setting up a pattern that references slices on one sample across 16 tracks so you’d just need to make a sample chain and load 1 sample into the same slot to update all 16 tracks

[mzero]

So, this isn’t all that hard to do…

1. Create a new project
2. Rename and load it
3. Clear the sample pool: Func+Samples > Project RAM > → (to get menu) > Select All, then Unload
4. Load up samples from the +Drive: Func+Samples > +Drive → (navigate to a folder of samples) > → (to get menu) > Select All, then Load to Proejct

This will load the samples into Sample Pool slots A001 upward for as many samples as you selected. As all the default patterns use slots A001 through A016 for the 16 tracks… yer set!

If you want to do this for an existing project… you can do step 4… and the samples will be assigned consecutive free slots in the sample pool. You can see the assigned locations right after you do the load operation. Now, go back to some pattern, and assign those samples to the 16 tracks, one by one. This part is a bit tedious, but surprisingly quick once you get the hang of it.

You can use the elk-herd beta to then load up the project, and see how the samples are sitting in the Sample Pool and easily move them around if you like, preserving the assignments in whatever patterns you’ve created.

---

Question for others: Would such a feature in elk-herd be useful for you? If so, I’d like to understand how you’d envision such a feature to work. DM me!

[etcetc]

Thanks! I’ve actually been using elk-herd and I also wrote a small local modification to allow me to only update one pattern at a time instead of processing entire projects.

To give some context, I work heavily in Ableton and use sample organizers like Atlas and XO to manage and classify my samples. The dream workflow is that I can generate new kits and them just instantly start working on them on my local project and pattern with the current sounds without needing to go through all of the above.

I tried to modify elk-herd a bit more to automatically upload to Drive, assign them to the current sample pool, and then assign 16 samples to a given pattern if you drag them in, but was having some trouble doing this, quite unfamiliar with Elm.