Eigenharp Tau gifted to me- but where do I start?

yeah we need to tidy this all up a bit…

there are really 4 ‘sets’ of files

EigenD - you should use community build, Eigenlabs not required :slight_smile:
runtime - basically this is python and can be sourced elsewhere
windows driver - only required for windows, I can probably throw this into GitHub, as its small.
resources - optional/not required.

extra notes:

runtime (windows)

I need to check to see if window can run from the 3rd party python install… it may need a tweak in where its picking up python from.

window driver

my aim is to remove requirement of this, by using libusb as we do on linux, then using libusb driver.
but for now I can host in GitHub as its tiny.
note: we do not have code for this, and its subject to licensing !

resources

this is currently
contains:
samples & convolution ir (for cello etc)
other resource files (scales?)
demo versions of vst

what I want to do is create a cut down version of this, that only contains license free resources, and is also platform independent. this means removing the demo vsts.
removing the demo vsts I deem acceptable because these are years out of date, doing so will mean resources have no platform dependent code, and also dramatically reduce size of resource bundle.
also removing vsts means there is no requirement for installation as everything then is simply placed in the eigenharp directory… so we can distribute as a simple zip file.

in fact if the resources are small enough (and license free) , I can included in EigenD package !

this could mean midterm (aka when I have time/motivation) you simply install EigenD, and python (from python.org)

long term… I still dont know, as the python 2.x dependency is a real time sink to fix… which I keep starting, but lose motivation are a week or two.

2 Likes