Elk-Herd 3.0

Heya,
Importing patterns works pretty well now!
The only thing that wasn’t imported correctly were samples that were only locked per step. The regular track samples were imported.
I won’t find the time to save step-by-step project files until next week though.
Thanks a lot anyways, great work!

just confirming: we’re those sample slot plucks, or sound locks?

Hi mzero, when I import a file to an existing project the new samples are added to the pool nicely. But the new sample positions are not stored correctly in the imported patterns. So on DT it plays other samples than it should. I am currently adjusting it manually on the DT as a workaround.
Apart from that - no question - you are a hero to me!
Enjoy your vacation . . .

And the same happens whem fetching a project from DT, delete unused samples and compact the pool. After sending it back to DT the pattern are not playing the samples as before.
All this is just for info. Overall I am very with the latest update and highly appreciate your work!

I’m trying the beta with 1.30 firmware and now fetching project is working but when I send the project to the DT the progress bar is showed only in elk-herd and in the DT nothing happens.
I appreciate the god job is doing mzero.

Sample slot lock.

I tried several things as change the USB cable and reinstall the 1.30 in the DT and now I can finally send back thee project to the DT.
Now I can see, as other people, that the sound locks doesn’t work. I can notice that the param lock “number of sample slot” is the same that in the original project but in this slot there is a different sample in the new project.

I’ve connected my AR MK2 to Elk-Herd, and all I can see the samples that I’ve recorded. Shouldn’t I be able to see everything that’s on the +Drive as well? :grinning:

No, whileelk-herd supports sample management on several Elektron boxes, it only handles full project data management on Digitakt.

4 Likes

Hey all - I’m back from vacation and spent today plowing into the issues you’ve all reported.

There is a new version up - just use the same URL, but reload in your browser.

Fixes:

  • There was a bug with sample plocks - now fixed!
  • Data is sent to the Digitakt with better timing. This fixes the problems people reported with the sample pool not being correct after compacting or importing. This also improves the Send Project progress bar - as it now stays closer in sync with the Digitakt.

As always - keep backups and let me know how it goes.

  • Mark
14 Likes

Hell yeah.

Update: Everything worked swimmingly. Why Elektron doesn’t hire you/buy the rights to this and make it legit, is beyond me. You’re epic.

4 Likes

Almost a total noob, so my assumption is that I am doing something dumb. However, I am having problems managing Projects. I connect the Digitakt to the PC, I can see all the samples on the +Drive and their folder structure. I click on the Projects tab and select Fetch Project, a progress bar appears and, well, makes no progress. I know one of the vids says it can take some time, but I took the dog for a walk and still no progress. Any ideas what might be the problem?
TIA
Tom

Let’s start with
Are you on latest firmware
Check
Double check

3.10 - that is the latest isn’t it?

er… uhm… no… There is no 3.10 firmware… did you mean 1.30? If so, you need to use the beta version of elk-herd:

https://electric.kitchen/crunch/beta/elk-herd/

Otherwise, you should be on 1.20, and use the normal version:

https://electric.kitchen/crunch/elk-herd/


In either case - make sure that no other software is using the Digitakt over MIDI (I’m assuming you are using USB midi here). Close Transfer is you are running it. If you are using a DAW and Overbridge for the Digitakt, then close the DAW (generally no needed on Mac, but Windows users seem to need this depending on versions of OS and DAW).

Also, on the Digitakt, check System :gear:> MIDI Config > Port Config, and be sure that both Input From and Output To are set to USB. It should also work with MIDI + USB but may be slower.

Transferring a project is not instant, but takes only about 15 seconds.

9 Likes

You-hero: Me-dick!
Thanks for your patience.

No worries - nothing wrong with being new to all this.
So - did you get it to work?

1 Like

Like a dream! I don’t know how many hours you have spent developing this and other applications. Is there a “tip jar” somewhere?

1 Like

Click on the small beer bottle in the upper right of the elk-herd app…

2 Likes

Hey Mark,

just want to share some findings I experience with the latest update:

  • when fetching a project from DT and send it back without changing the sample pool there is no issue at all
  • when selecting and removing unused samples, in the elk-herd sample browser also the samples are removed that are used via parameter locks. But when I send the project back to DT these samples are still in the pool, allthough they were not shown in the elk-herd sample browser any more. Also the patterns still play as they should since all samples are still there.
  • but when selecting and removing unused samples and then compact the pool it is different again: the DT sample pool is the same as it was shown in the elk-herd and the patterns are not playing as they should - it is all mixed up.

I hope this can be helpfull information.

Big Respect and Many Thanks!

Andreas