Elk-herd 3.3 Release

Hey there, I can’t fetch a project regardless what I do. I’m on 1.10 os/ windows. I tried Edge and Firefox but both showed an error message

I can see my samples in the drive but that’s as far the functionality goes for me :slightly_frowning_face:

If the +Drive loads up correct, but not the projects… it is probably the very large SysEx giving your MIDI system fits.

Please DM me the details of the error message. And then I might a few other ideas.

Other Windows users: Is there a way to ensure large MIDI messages get through? On Linux we have to increase the MIDI buffer sizes – Is there something similar for Windows?

What about Chrome?

@mzero Thanks for this project! I assume I have not missed a functionality to preview samples within Elk-Herd? Probably out of scope :smiley:

I suppose I can try having Transfer open simultaneously and hope there’s no glitching.

1 Like

Hi! I’m using a Digitakt, connected fine with Firefox, direct USB to computer, tried using DT set to Overbridge or USB Audio/Midi, but I get a timeout error when scanning particular directories on the +Drive. Have tried with the startup flag of a longer timeout.

I can see ~6 preceding directories have scanned in fine, but when it gets to my ‘808’ directory it fails. I tried removing the unused samples and it works, but then gets stuck on some of the samples in my ‘909’ directory.

Have attached a zip of the ‘808’ directory in case that’s useful to pinpoint what Elk-herd doesn’t like about the sample files. I noticed in File Explorer that some of the wav files have extra metadata in them, like ‘Album’, and I tried getting rid of those and re-scanning but the same problem occurs.

808.zip (8.3 MB)

1 Like

Not sure how you’re setting the timeout… but the method changed in v3.3:

On the Settings page, there is a box labeled “Optional flags:” at the bottom. In there, try this:

retryInterval=10000

That is a value in milliseconds, and 5000 is the default setting. Sometimes, the DTs take a long time to respond when a directory has a really large number of samples. If 10000 doesn’t work, you might try as higher.

Most people have had better success with USB set to Audio/MIDI or MIDI rather than Overbidge.

Also, make sure you are not running Transfer at the same time.

I will try out that archive on my machine…

3 Likes

Once uploaded to the Digitakt… all the meta data is removed.

When elk-herd scans the +Drive… it isn’t looking at the sample data at all, just the directory listing from the DT.

3 Likes

Thanks for the fast reply!

Sorry, I should have said I tried the optional flag retryInterval=15000.

Tried with no Transfer running and with Audio/MIDI in USB config, no luck so far.

That’s good to know about the metadata being removed on import to the DT.

@mzero you da man! Thanks a lot for putting the time in saving our chaotic workflow ^^
now I can finally put together ONE project to play live with instead of having to adhs my way through about fourteen projects to in the end not find what I’m looking for in the first place bc distraction kicks.

Lif/vesaver. :fist_right: :fist_left:

3 Likes

It seemed to be working fine for me with 1.10 even before the fix. Thanks for doing this. I couldn’t believe how well and smoothly it works.

3 Likes

WoW, so great ! You´re a hero.

bought the DT2 last october. tryed to load my samples into it.
The experience was horrible. Never used the DT2 ever since…
i´ll start fresh now.
Pizza and Beer was just sent by PP !
Muuuuch appreciated !

2 Likes

Hi, Mark, (and all digitakt users, dave mech!) thanks for all the work… Im not a very under the hood musician, I dont have a github account, so im posting what might be a simple? problem.
each time i fetch or import a project, elk herd says “the project is from an older verion of the digitakt than your machine”, even when i know that said project is one i just made on the same machine (i have a Digitakt2, 1.03A. mac using sequoia, on chrome, and chosen usb audio/midi on my digitakt config) it suggests I send the project back to the machine to upgrade, which ive done, but no change.
i tried following marks instructions to on how move patterns from a hypothetical "ideas"folder to a “live set” folder, but that resulted in the prefigured sample set only importing into my new project.

hope im being clear enuf!!! please excuse this old indie dudes attempts at grasping what might be obvious to some.

Hrm… that’s strange… I shouldn’t be possible to have older versions than 1.03A - since those versions (of the data structures) are version zero!

Anyhow…

The message is just a warning. You can safely ignore it. Just act like all is fine…

You can help me by doing this:

After you fetch the project from your Digitakt II, use the “Save File” button to write that to a file and send it to me (use the messaging system on this forum to send me a private message.)

As for importing things from one project to another project: When the import view is up (You see a big red Import banner at the top) you should select the patterns you want to move. In the right side of the Patterns header, it’ll say how many patterns it will copy. If you don’t select any, nothing moves.

If you’re doing that, and it still doesn’t work, please send me
a) a screen shot of the import screen just before you click the Import button
b) a copy of the project that you are importing into (fetch it, then use the Save File feature)
c) a copy of the project you are importing from (if you don’t already have this saved as a file, import it, then Save File).

2 Likes

thanks mark , not sure how to private message here.

Click on my image… Choose Message in the small window that pops up

2 Likes

Updates: Two bugs squashed!

However - I’m in NYC for week without my Digitakts, so I’ll put these up as a beta in a day or two. When I get back home I’ll thoroughly test the fixes.


Bug 1: @duende3000 reported upon fetching a project, elk-herd gave the message:

This project is from an older version of the Digitakt OS than your machine

This should never happen!

Turns out you’ll see this if you are running a Digitakt OS older than the lastesr version elk-herd can handle for your machine. By design you should be able to use elk-herd with older OS versions. (I know what it’s like to be a gigging musician and not want to upgrade until after the gigs are done.)

If you see this, you can mostly ignore it. The only thing you might encounter is that if you delete a pattern, then the empty pattern that replaces the deleted pattern may be unusable on your machine. Also don’t use the Clear Project button, as you’ll end up with project that your machine can’t read.


Bug 2: If you have a original Digitakt project that you used Transfer to send to your Digitakt II, and then loaded that project, and then fetched that project with elk-herd – All the empty patterns will show as phantoms (named “UNTITLED” in grey).

Phantoms are patterns that have no name, but don’t look to elk-herd like they are empty: They have trigs or non-default kits or midi settings.

If you see this, you can (assuming you know those are empty patterns), safely ignore them.

If you need the space to import other patterns, then select them and delete them in elk-herd first.

Thanks to @philipp_b for reporting the issue and giving me projects to debug with.

6 Likes

I’m living on the edge…
I reviewed the changes this morning, and decided to just push them live.

@duende3000 & @philipp_b - If you use elk-herd now, your issues should be solved:

  • Instruments with older OSes should not receive an odd warning
  • Empty patterns in DT 1 projects imported into DT 2 will now be correctly detected

Everone else - If you notice anything strange, let me know!

6 Likes

Hello! This might be a stupid question, but in a nutshell, does elk-herd do anything more that I can’t do with transfer for the RYTM?

Apologies if that has been answered already. :man_shrugging:t3::slightly_smiling_face:

In a nutshell - yes

Well? Enlighten me, please?

For the RYTM, elk-herd will allow you to manage samples on the +Drive. While the functionality is pretty much the same as Transfer (upload, download, move things around) - elk-herd takes a different approach to the UI.

Transfer is like the old “Norton Commander” file manager for (ahem) MS-DOS, famous for it’s two panel interface, looking at two directories at a time.

elk-herd is a more, modern style, with a full hierarchical list of the +Drive, which you can simple drag and drop to/from your OS’s file folders. Re-arranging things on your +Drive is simply a matter of drag-n-drop in the elk-herd window, too.

“Differen’ strokes for differn’ folks.” — “Let a thousand flowers bloom.” — “Try 'em and use whichever you like.”

8 Likes