it looks like Eigenlabs are letting there forum and website lapse. as has been discussed here, so we are getting a few topics requesting help due to missing resources etc.
This topic is a WIKI, which means the community can edit it, and help keep it concise.
Its pretty bare bones at the moment, limited time, but if others would like to update/embellish, that be great - particularly on the windows side, which I rarely use
(replies/posts can discuss this, or add some extra info as required)
the latest version of EigenD is the community edition, as its available from
this contains many bug fixes, and is working on modern platforms.
PLEASE READ THE INSTRUCTION THAT ARE SUPPLIED, there ARE extra steps required.
for references you can read this here
on macOS the community build uses the Python 2.7 already pre-installed with the OS.
for windows, if you do not use the runtime package you will need to install python 2.7 from python.org
Mac is ‘driver free’, but Windows (currently) requires an Eigenharp driver to be installed.
you can get this from here
No resources are required to run EigenD, however the factory presets all be missing samples and certain (demo) vsts. however, you can use your own by updating the preset (in workbench).
these are noted in the README provided in the EigenD distribution.
the python based browser/commander applications no longer supported.
this is due to the (old) python libraries used, and distributed in the runtime install.its unlikely this will change. use Workbench instead.
note: if you are on windows you could use the runtime package, but this is not supported.
iOS app, this should continue to work, however its no longer on the App Store, and is no longer supported.
as a community we are starting to develop some alternative applications use your Eigenharp with, that don’t rely on EigenD (or python). these may well be the ‘future’ of the Eigenharp, as they are built on a more supportable platform.
(to do : add links to relevant topics)
I recognise all of this is more complicated that many would like, as today we are used to one click installs. but this is now more of an ‘enthusiasts’ project, where time is limited.
the main focus now has to be, to ensure, in the future we have everything we need to continue to use the Eigenharp with less possibility that OS and 3rd party updates will break them - basically, make it easier to support with less dev resources.