I began the open core legacy patcher process, but eventually got a bit confused. My 2017 iMac is stuck on Ventura. I will have to give it another go and keep at it when I have the time. Is there a good ‘explain it like I’m 93’ tutorial somewhere? (I’m not, but…that would be ideal, lol.)
Hello everyone,
Since the recent update 1.15 on my Digitakt 2, the “Fetch Project” function no longer works.
I get the following errors:
“Error in received project”
“An unexpected dump type was received”
Browser: Google Chrome
Operating system: Windows 11
Does anyone have a tip or solution?
Thanks!
The solution is: Wait.
Thanks
Scroll up a little and there’s a post saying he’ll get round to it when he’s got time
I am also getting this message. Using chrome and firefox on a mac pro, all updated, Digitakt 2 on 1.15, using a USB hub as my macbook only has USB C ports and the elektron wires are oldskool USB wires. Wanting fix this to donate some beers. regards
Sorry this has taken a little longer to get to than I had hoped… (but yay… Summer fun!)
I’ve got all the changes in to support Digitakt II OS 1.15 done. Now I’m debugging reports that handling of p-lock’d samples is broken. Assuming that bug isn’t too buried… expect a release this week.
Until then… if you’ve updated to OS 1.15, you won’t be able to use elk-herd.
Still no app for Android
Thank you again for the massive service you’re kindly offering the community.
Since I last checked in I’ve gone and acquired a DTII, and have found the need to move patterns around a project.
First thing I did was naturally to check elk-herd
elk-herd should work under Chrome on Android. That said… the UI isn’t really built for phone sized screens, but might work on a tablet.
Thx for the reply
Almost there…
I have fixed two things:
- Support for DT II OS 1.15 and 1.15A
- Fixed a nasty bug that crept in back with support for DT II (see below for details)
Pretty sure this is all good to go, but let’s run it in “beta” for a day or two first.
Update Aug 3, 2025: Now released:
The nasty bug
Since elk-herd version 3.3 (March 2025), for Digitakt (original) projects, elk-herd stopped tracking p-locked samples. This had several negative effects:
- Selecting (or hovering) patterns didn’t highlight samples that were only p-locked as related.
- If you moved p-locked samples, the p-locks didn’t get fixed
- If the samples were only used by p-locks in the whole project, then elk-herd would let you delete them
- Importing patterns wouldn’t pull along p-locked samples, nor fix up the p-locks.
This bug didn’t affect Digitakt II projects.
Thanks to @LLLL, @YilmazPeksen, & glenpike (on Github) for submitting bug reports. I apologize I didn’t recognize the severity of this bug sooner.
Tried it yesterday with the DTII and I’m also getting the error Project dump does not have all the patterns
The same setup (computer with MacOS 14, USB A-C adapter and Brave browser) worked with the OG DT though. The sample pool on the DTII is a lot more populated, that is the only difference from what I can tell.
Will I be able to move patterns from the OG DT to the DTII once I got this running and they’re both connected at the same time? That is my main task atm.
It might be worth using transfer / the elektron suggested method to take dt1 projects to dt2
And then use this to move patterns etc once it’s updated and tested
Only had a quick look into this but haven‘t found anything useful yet, will look further into this. Thanks!
Mac OS 14 has a very nasty bug in Apple’s Core MIDI USB implementation.
The bug means that Apple can’t reliably transfer large (> ~60k) SysEx messages, which of course the Digitakt II needs.
There is no fix, and pretty sure Apple will never fix it. It is fixed in OS 15.
elk-herd won’t let you transfer DT 1 projects to DT 2. That has to be done with Transfer. Transfer will move the DT 1 project to a +Drive project slot… then when you load that project on the DT 2, the instrument will convert it.
But details:
Can you query what os version is running and pop up a message for macOS 14 users related to large file size issue ( and blame apple ) ?
Were it only so easy! Robustly detecting the version of the OS the user is running is well over 100 lines of code! And even then it is a mess of regex matching dozens of odd cases because none of this was standardized. And even if you go to all that trouble… the value isn’t definitive!
sounds like my bank statement.
It’s what you would expect, just use transfer to put your DT1 projects onto your DT2 … BUT … there is a quirk, which needs some follow-up. If you don’t then save the project, it won’t be backed up.