I have a Mac based on ARM, can somebody point me to the Software (or SDK) for the Pico? If it is Opensource but back level I probably could update it.
Sorry if this is a stupid question, but I am totally lost, got the device gifted, was never used before. I used to play the clarinet so they gave it to me…
1 Like
this gives instructions on how to install Eigen (the community version) on the Mac etc.
its not native apple silicon, and cannot be for a number of reasons Ive discussed before on this forum, so a search will give you the background.
tl;dr; there is python dependancy which means its not just a matter of recompiling - significant development would be required.
the above also gives you a link to the source code , but unless your up for an extreme challenge, Id not recommend trying to build it.
there are also a couple of community ‘alternatives’ to EigenD, which are lighterweight e.g. ECMapper / Meta Morph / Mac which you can find links to.
I developed a lightweight interface to the eigenharps called EigenLite which you can use if you are a developer.
a quick search on this forum will provide links /information for all the above.
1 Like
Thank you, very helpful.
I will have a look into the code what the python dependencies are and if I make some progress I will let you know!
1 Like
the main issue, is you’d need to move from python2.7 to python3, and given the code base this is non-trivial
I documented the last attempt I had at it - you’ll also find a python3 branch in GitHub (untested and incomplete !!!)
https://community.polyexpression.com/t/eigend-upgrade-to-python-3
also its not just python code that needs to be updated/modified…
EigenD integrates python and c++, in a multithreaded environment, which has important issues/limitations for python.
before the python 2 eol, I tried to upgrade to the latest version of python 2, and found that this introduced (new) thread blocking issues due to this, and I would expect the same is true of python3.
so its non trivial,
you’ll need experience of C++ / Python with multi-threading experience to get anywhere. also there is a lot of pretty complex code, it also has a pretty archaic build system (scons) - but feel free to have a look / go.
btw: due to its complexity, I wont accept any automated converted / ai generated code into the repo - theres just too many ‘gotchas’ that would cause bugs, that’ll be nigh impossible to track down.
ofc, in your own fork you can do what you like 
as Ive mentioned elsewhere, I keep going around in circles on this one.
on one hand, EigenD is pretty good, and is ‘feature rich’, so Id love to get the code base built on moderns tools etc. so… Ive tried this a few times.
on the other, the code base is very difficult to work with, and I often think its easier to build what I need from scratch using EigenLite.
so, this has led me to create various projects based off this approach.
personally, at the moment, Im leaning more to the latter.
I think having applications with fewer dependancies, and a more focused code base is a better / more supportable solution.
anyways, as I said, Ive made plenty of posts on my thoughts, and also the current situation/issues with the code base - so Id advise checking those out before diving in… as it’d easy to spend a week messing with code, only to find out complications Ive already posted about 
1 Like