Where next/future?
so the above raises a few questions/ and thoughts.
I’d like to make the EigenD distribution be ‘complete’ for essential parts.
I think this means, including in the EigenD distribution
a) Windows driver (short term, see below)
b) Convolution samples
as you can see, this is the bare minimum… not every sample, nor vst, nor python runtime.
these would be ‘extra steps’ for users to handle… and this is probably what we need to document better.
EigenD is ‘safe’ we have the code. however, its dependancy on Python 2.x is becoming a big issue.
a couple of times, Ive started to port it to Python 3.x , but Im not sure if my heart is really in it.
its tedious, and frankly, I think could take a lot of dev effort. BUT Ive not made a final decision on this.
I want to remove the Windows Driver dependancy, as we dont have the code for it.
for Linux, we are using Libusb in the EigenD core code. in the past, I’ve experimented with this on Windows and it works too…
the principle then is, users will install the generic libusb driver for windows, which will be ‘future proof’.
there are a couple of step to do this
i) I need to put the necessary changes into the eigenD mainline codebase, and release
ii) we need comprehensive user documentation on installing and setting up windows libusb driver.
iii) testing - on different systems, and also for performance. ( * )
( * ) as I said, it ‘works’, but have ever checked its performance - that said, theoretically, Id expect it to be better not worst… also testing on one windows machines is rarely representative for others 
so to (new) users , what the above would give is.
- download/install EigenD from my repo.
- read documentation (!)
- install other required components (Python and libusb driver for windows) from named sources
- window users setup libusb.
if they want to use,
Limitations
- only modern OS support (32bit)
- users will have to read instructions and follow, its not just click n’ run.
unless someone else in the community wants to do this, I don’t have time - modify factory presets
Im not going to distribute old vsts/samples, so where these are used, users will have to
again, the community could contribute new/updated presets if they wish to improve this situation.
I do understand this is putting a lot more on new users, and I can see that being unpopular.
but honestly, like most ‘ageing’ tech, really I think the focus has to be on enthusiasts now… users that wiling to invest time to get things going.
that may seem ‘elitist’, but remember, the support and dev is now coming from enthusiasts too, we are not paid/profit from this… so we have to consider where we want so spend our (free) time/efforts.
Hardware support
ok, not much to say here…
if you Eigenharp develops a fault Eigenlabs is still really your only point of contact, we have no schematics or anything for the hardware.
AND if you open the Eigenharp officially, it’s likely it will need recalibration which is something only EigenLabs can do, with a special tool/jig they have.
but so as to keep information together, and Im going to link to a recent post, about some investigations Ive done into re-calibration of Eigenharps