Outstanding work. Hope to check it out soon. The ability to grab patterns from different projects into one new project is awesome and something I do manually now which is quite tedious.
I also have a Excel sheet where I keep track of all samples and sample locks to know which are in use etc. So having that functionality automatically, and funnily enough with the same color scheme, is quite incredible. Thank you for sharing!
Cheers!
Just tested it and its working super well! I did try it while my pattern was playing and the DT froze however. I didn’t lose any data though! I rebooted and tried it while it wasn’t playing and had no issue.
One wishlist feature I would love would be a tool to copy just the kit information to another pattern. The kit implementation on the DT seems half-finished, you can save and reload just kit information, but you can’t simply copy it to another pattern. If i had a way to keep kits (ideally with midi page info too!) across multiple patterns with slightly different sequences in sync, that would be super dreamy. Not sure what’s available regarding kits in the secret API you’ve found though.
Keep up the awesome work!
Just a reminder: This functionality isn’t in the alpha release… but will be in the beta!
Curious - did it freeze while fetching from the DT, or when sending?
I have access to the kit data (which includes MIDI track settings) separate from the sequencer date. elk-herd could easily let you copy kits from one pattern to another (audio tracks, MIDI tracks, or both)… though the UI might get increasingly more complex… As for how to keep them in sync… well that’s more complex…
Great 
will wait for the beta. Looking forward!
3.0 alpha 2 is up - just reload to get it!
Hi! thanks for the fast response, but that is still not working. I thought that the problem might be with JACK, which is a sound manager for linux (http://jackaudio.org/) so I tried without it. And still having the same problems. i guess it has something to do with sending MIDI through Chrome, even if I allowed it :-/
I also tried setting input and output to USB.
It happened while writing the project to the DT when the pattern was playing, the DT showed “Received Pattern AXX” for a bunch of patterns and then eventually froze. The strange thing was that the audio continued although the display was completely frozen. Rebooted, tried to write again without playing, and it worked fine.
I didn’t mean keep them in sync automatically, just that it would be awesome to have a way to copy kit data from one pattern to another manually, with fewer steps than what I’m currently doing. The simplest UI I could imagine is that whenever you come up with the “copy pattern to another project” workflow, you have the ability to copy just the kit or the kit and sequence data. (That assumes that the copy pattern flow would also work inside the same project). I do understand that this is probably low priority next to other things you want to build, but just food for thought!
Any chance of going open source with this project ?
thanks for your work anyway 
- I’ll pull out my Linux machine today and see what I can find. I generally use ALSA for MIDI, and only use JACK for audio… but I’ll see if I can get both working.
From the github repo for the project (mzero/elk-herd.project):
Why do I see no code checked in here? Because the project is not currently open source.
Why not? I had to work out the protocol to the synths on my own, as Elektron isn’t ready to support it publically. I respect that, and don’t want to make the protocol public by releasing my source code. Elektron is committed to eventually making an API they can support, and at that point I’ll be happy to open my source.
Small update: alpha 3 just pushed to support 1.11 beta 6 OS. You really should upgrade to 1.11… but some folks haven’t yet. Which I get: Sometimes you are in the middle of working on a piece and don’t want to rock the boat on your instruments!
Hi Mark,
gr8 project! I’m extremly interested in sending samples to my digitakt from my GNU/Linux machine. My Digitakt gets detected, can send samples, but couldn’t receive any sample i tried so far (48kHz, mono), with the stable site also with this alpha. My firmware is 1.11, and i use Debian 10 amd64 with chromium 76.0.3809.100. If you need any more info i am happy to provide it.
Greetz,
DNS
Don’t know if it matters, but in Chrome, you can allow/block web Midi access if you go to:
Preferences (Settings) > Advanced Settings > Site Settings > Midi Devices
Maybe that will help? Good luck!
Nice job Mark, you are amazing, Elektron will be trying to steal you away from G here pretty soon with a juicy job offer.
I wish you would open source this, it would be a nice project to learn Elm on … Although I understand if you won’t.
Edit : on the upside I can help with bugs
Linux users: I have reproduced the problems on my linux machines, and will look into what I can do. Sadly, I’ve found a bug report in the Chromium repo that implies that Chrome on Linux has problems with large SysEx messages… I’ll see what I can do for a work around…
D’awwwww… thanks! Actually, no stealing required: I left G at the start of the year to have full time to devote to music making and music technology!
See post #49 above for reasons why open source will come later.
Oh wow congratulations on your new-found time! I was wondering how you were able to manage work, this project, music-making, and real life to boot. Excited to see where this project goes, I can’t imagine that Elektron doesn’t want you on the team.
Just unreal work mzero. What a talented person you are!
My DT gets detected, can send and receive samples (so, elk-herd 2.0 works good), but cannot receive projects althought projects can be sent from DT to Chrome . I am using Linux Mint 18 Cinnamon 64-bit wit a lowlatency kernel, and chrome Version 77.0.3865.90 (Official Build) (64-bit).
Hopefully you find an easy and nice workaround to this. That doesn’t sound so good :-/
Thanks again for not forgetting us, Linux users. Usually everybody forgets us.
excellent work man! thank you so much for sharing. ill be able to dive further into it next week.
Hi elektronauts!
This was happening to me as well. The problem, as seen on the kernel log, is a “MIDI output buffer overrun”, which is probably caused because Chrome is using the ALSA midi sequencer interface instead of the ALSA midi raw.
The solution is to split the SysEx message add a pause between every fragment to let the buffer to be transmitted.
To overcome this limitation, I have developed a simple transfer application for Linux, which is available at https://github.com/dagargo/elektroid. Be aware it has not been properly tested yet, so run it under your own risk
I hope Linux users find it useful.
Would love to see this kind of app for the Analog Rhythm as well 