EigenD - custom midi output

The instructions for installing EigenD are great, but I ran into an issue where the closed source Eigenharp driver wouldn’t auto install. I had to click ‘see details’ to locate the install directory, then went into \Program Files (x86)\Eigenlabs\driver-1.0.10 and had to run ‘dpinst.exe’ as administrator before the driver would correctly install. I didn’t see any mention of this step, so it might be a new thing that Windows 11 is forcing people to do.

I’m now at a stage where I’m completely stuck. I need a completely new workbench preset written, where each of the rows transmits chromatically on its own unique midi channel, and where the scaling is reversed from the standard. I’ve tried to explain what I need in this short video - https://www.youtube.com/watch?v=0ilVb0NtFsA

I don’t need any menu options on the Tau itself, as I can transpose within Ableton Live itself. I just need the Tau to act as a simple midi controller. Is there anyone who can help me with this? Trying to understand Workbench just destroys my brain.

Thanks in advance x

ok, Ive moved this topic away from EigenD 3.0 Beta, as Im assuming you are trying to install 2…1.7 as the 3.0 beta does not at this time support windows.

so I assume you are following along with this topic

note: Ive updated the above topic, to point at 2.1.7 release, rather than ‘latest’, as this is more appropriate, outside of EigenD 3.0 Beta

so you should pickup EigenD 2.1.7 from

yeah, Id assume thats always the case… or at least that windows would prompt you to install as admin. generally windows has tightened up the ‘user = admin’ over the years :wink:

ok, so the first question is … are the factory setups working?
there is no point, in proceeding with modification via workbench, unless we are certain everything is working correctly before hand.
i.e. are we just talking about how to use workbench to achieve what you want or an issue?

I’m now at a stage where I’m completely stuck. I need a completely new workbench preset written, where each of the rows transmits chromatically on its own unique midi channel, and where the scaling is reversed from the standard. I’ve tried to explain what I need in this short video - https://www.youtube.com/watch?v=0ilVb0NtFsA

Ive not watch the video (yet) …
but when you say ROW, to you mean down the Tau? or across?
(as Id call that column … then again, I cannot remember which way EigenD calls it :laughing: )

basically, if you want to have separate midi channels. then its going to get fun…

Id start by looking at the basic midi factory example, to get yourself familiar with the modules you are going to need.

essentially what you are going to need to do is, create a keygroup for every ‘row’ (i.e. what you want as a midi channel), in that keygroup you list only the keys that you are interested in (i.e. that row)

then for each of those keygroup, create keygroup output then send to a scaler, then midi converter, then finally midi output.

each scale you configure for chromatic and octave, each midi converter midi channel etc.

basically , its like the midi example, except you are going to have multiple keygroups.

so

keyboard → keygroup 1 , keygroup 2 , keygroup 3 , etc

(Id probably actually go keyboard → Keygroup Main → keygroup 1 , keygroup 2 , keygroup 3 , but I suspect that is not ‘necessary’)

keygroup N → output 1 → Scaler N → Midi Converter N → midi output N

i guess, the other way, if you are not confident with this, and the you are already doing mapping in Ableton, would to be just use the basic midi example.
that could be seutp to send different midi notes for every key (as tau has less < 127 :)) , then map from that.
thats pretty trivial to do, just change it so the offset is number of keys in a column

Thanks for your reply Mark, and thanks for moving this to a new thread. I couldn’t see any recent threads for v2 and I wasn’t sure if my request deserved a new thread.

Re: rows, yes, it’s the long rows across as opposed to columns, and because I’ve positioned the Tau so that the main playing keys are under the right hand, the scaling needs to be reversed from the default.

EigenD works fine, and I can play sounds through EigenD using the Tau, and I also remember how to get midi into a DAW by routing everything out of EigenD and into a virtual midi interface like LoopBE. It’s just the preset that I’m having difficulty doing.

If a seperate midi channel per row is difficult, is it easier or even possible to set up the main keyboard on MPE lower and the 12 large pads on MPE upper, so that I can use one for instrument and one for drums at the same time?

I’ll digest your reply a few times and dive back into Workbench. Thanks!

yes, thats possible even in the tau factory preset.

the tau factory preset has 2 midi rigs.
so to get what you need , just use the standard ‘1 split layout’.
then set the main keygroup to use midi rig 1
and the percussion keygroup to use midi rig 2.

this is described in the tau quick start manual.

midi rig 1 uses midi converter 1 (and output 1),
so set converter to use MPE lower ( I call it MPEa)

midi rig 2 uses midi converter 2 (and output 2),
set converter to use MPE upper( I call it MPEb)

then you can set the min / max midi channel on each to ensure you don’t overlap.

that said, if you are using LoopBE, then Id just use MPEa for both, and send to different virtual midi devices (MPEb / Upper is not well supported, so I avoid !)

IF you’d prefer something that loads quicker, you should be able to Experimental Tau Midi Basic, that doesn’t have any ‘extras’ , just midi rig 1 on main keys, midi rig 2 on percussion keys…

midi basic, is quicker to load and would be easier to edit, if you wanted something slightly different.
the factory setup is more comprehensive, and has documentation :wink: