Elk-herd 3.0 beta: Project Import at last!

[whhbaa]

Thanks for the quick response and update. All the love

[BadgerFox]

Just got a Digitakt and getting into it. I can see this being amazing the further down the line I get. Thank you!

[martibs]

I’ve been experimenting with improving audio performance on my Ubuntu system, changing a whole lot of settings and adding/removing features (don’t do this at home kids (at least not without backup first)). Now I get this strange error message when I try to run elk-herd:

I guess this is from the web-midi which is no longer working due to some dependancy?

(I’m not expecting a solution from you here, @mzero, but maybe you have a clue where I should start troubleshooting?)

[mzero]

elk-herd needs WebMidi which means Chrome which needs ALSA.

Chrome uses, as far as I can see, the raw MIDI facilities of ALSA, but perhaps also the ALSA Sequencer facility. You should keep both of those in your kernel¹. As far as I know, Chrome’s WebMIDI doesn’t make use of any helper executables, just the features in the kernel.

---

¹ I actually don’t know if you can configure these independently for your kernel or not, but if so, keep both.

[mzero]

Thanks to a bug filed by @flux-us, I’ve found a small issue:

• If you reorder or compress sample slots, and sample slots 1 ~ 8 move or change…
• Then send that project to the Digitakt…
• And later fetch that project back from the Digitakt…
• You may find that all your empty patterns have become phantoms. That is, they’ll be called “Untitled” and be shown in grey:

Your other patterns will all be fine. These phantoms can be removed by simply selecting them, and deleting (the × icon in the right of the Patterns title bar), and they’ll restored to empty patterns.

Will be fixed before final release.

[martibs]

Sorry for going off topic with this one, it seems to actually be a bug in Ubuntu 19.10, which now installs Chromium via Snap. So if anyone else is having problems with Elk-herd running on Ubuntu 19.10, check this bug tracker:

[HiGrade1]

@mzero

Will be fixed before final release.

Is there a projected date for a final release? Not to rush you kind sir, please take as much time as you need… I know this is not a simple thing you are doing. Please know that all your efforts in creating this massively helpful utility are greatly appreciated.

[mzero]

I gave a recent performance in Phoenix, and so things got away from me these last two weeks…

I’m planning on releasing 3.0 this week.

There will be two things left out, slated for 3.1:

1. Some way to work around the issues on Linux w/Chrome.
2. Better support for sounds where LFO modulates Sample Slot

[HiGrade1]

Thanks for the update!

[barba-ex-machina]

I solved connection & transfer problems on Linux / Chrome by increasing the MIDI I/O buffer sizes from 4k to 64k. The default is apparently too low.

Run the following script as root, after connecting the DT:

#!/bin/bash

dir=/sys/module/snd_seq_midi

if [ -d $dir ]; then
  echo 65536 > $dir/parameters/input_buffer_size
  echo 65536 > $dir/parameters/output_buffer_size
  grep ^ $dir/parameters/*
else
  echo Module snd_seq_midi not loaded
fi

[martibs]

I’m having an issue with some samples ending up distorted after I transfer them onto the Digitakt using elk-herd. The issue has been present on both combinations of Linux/Chromium/elk-herd2 and Linux/Chrome/elk-herd3.

Some artifacts are added to some, but not all of the samples after I do a mass transfer of samples. This is an example of a sample with such a distortion:
Original sample on disk:

Sampled transfered to and played back from Digitakt:

I’ve never had this issue using Elektron Transfer. As nobody else are having this problem, I’m suspecting it might be due to the settings on my Digitakt, but I’m not sure exactly what they should be set to. I have “turbo speed” disabled, and “input from” set to USB. Anything else I should look for?

[mzero]

There is definitely some sample corruption there, but because it is a recording of the output from the DT, I can’t see it directly (only the result of it post audio chain). Can you use Transfer to copy the sample back from the Digitakt to you computer and give me that? I can then see the nature of the corruption, which will help me diagnose the problem.

[martibs]

I deleted the corrupted sample, so I did another transfer, this time using Windows/Chrome/elk-herd3. Here there were also a couple of file corruptions:
Original: https://eu5.dh-cdn.net/uploads/db8181/original/3X/b/8/b8df21c49ffd9663124504aecb67bb01393f5104.wav

Copy: https://eu5.dh-cdn.net/uploads/db8181/original/3X/3/1/31fb35b8c26e624b395496695f1e492b575c947a.wav

It seems to be consistent that there is a click in the beginning of the waveform on all the corrupted samples, but I’m not 100% sure.

[mattp]

Hi I’m just trying elk-herd for the first time and I really like it. Thank you

Would it be possible to add project management as well please ? So you can rename project etc

[mzero]

I’d love to… but I haven’t found a way to get the Digitakt to give me that information. I am in contact with Elektron, and they know about the need to make those APIs available in the future.

[mzero]

Release Candidate 1 is now up. Barring any other issues this will be 3.0

Bug fixes:

• Don’t modify empty patterns when rearranging the sample pool. This keeps empty patterns pristine. Broaden the test for empty to include previously “shuffled” empty patterns that this bug created.
• Don’t get stuck when loop-back ports are selected (like IAC Bus). Now just give a clever warning.

Minor improvements:

• Cleaner handling of non-sysex messages
• Individual help topics can now be linked to
• Improved editing of pattern and sound names, keeping the cursor from jumping in more cases.

---

I still haven’t found a reliable set up for Linux… sigh…

[HiGrade1]

MZERO for the win!

[trashbin]

Hello mzero, you made brilliantly what I was requesting Elektron at last month. Congrats!
it’s possible to use it offline? Most of the users nowadays aren’t much concern by sharing data as they should be, but this is important to me, and that’s why I’m on hold on this topic. Does it work with other devices or just DT?
best

[mzero]

1. The on-line version sends only a small amount of anonymized stats data to my servers¹. You can opt out of this on the first screen, or later by choosing the [App Settings] command button.

2. You can download the web files from my server, already packaged up in this tarball: elk-herd-live.tgz. Just unpack it and open index.html in your local Chrome browser. This version will still try to send data back if you opt-in, but it won’t complain a wit if you are disconnected from the Net.

3. +Drive sample management works with Digitakt, Analog Rytm, and Model:Samples. Project and Pattern management is Digitakt only at present.

---

¹ — It sends the name of the browsers, the version of elk-herd, the name and OS version of the synth, the names of the MIDI ports used, how full the +Drive is, and periodically, counts of how often each command was used. All of this is identified with a random number (UUIDv4) - and no personal information is collected, asked for, stored, or transmitted. — I spent several years working in the area of web security research. This stuff matters to me, too!

[Jack_69]

Hello, fisrt of all thank you for your awesome Software.
I am reorganizing my projects and cleaning up my Digitakt after 2,5 Years of composing on that thing.
By doing this i experienced some difficulties when fetching the project, deleting unused samples, reorganising them and sending it back. Most of the times the patterns get all messed up. If i fetch the organiyed project back and send it again it works, but not always.
And when trying to get more projects together, the samples get not mangeled together on the digitakt.

Im runing osx Catalina with a 2018 MBP Touchbar and on Chrome. I also Made sure on the Takt to send and recieve Midi via USB and MIDI.

Am i doing something wrong?

Greetings and thanks agasin for your big work