Ive had EigenD compiling running on a rPI for quite a while…but honestly I don’t use it.
the reason is EigenD really needs a GUI, so xwindows ( local , virtual or remote you choose ) , and it’s just a bit too heavy for the rPI, esp. if you just need OSC/Midi.
I use MEC, which is pretty lightweight and gives me both Eigenharp and Soundplane , throwing out both midi and osc (t3d) - this Ive then been using in Orac/PD (Organelle and rPI) and also on Bela.
I’ve thought about Norns integration,
this would not be difficult as MEC runs as a ‘library’ as well as standalone app, so I could embed into Matron very easily, but architecturally its a bit ‘meh’ - norns uses a single event queue and processing thread for lua - hit that with lots of events and its not going to be pretty.
(remember we are talking a rPI, single core here!)
Ive ideas about to sidestep matron/lua and go directly to the sound engine (sc) , which would improve that - but thats a bit more effort, and is pretty norns specific.
I dunno, I don’t find myself using Norns, but I guess if one day Norns becomes more useful to me, I might give it a go.
for now, my priorities are Orac/MEC, which I use quite a bit… and has its own following
who knows, Ive so many ideas in this area esp. now with modular, its all comes down to what I fancy spending time on!
(*) you have to be very careful with eigenharps as the rPI , as the rPI kernel has a really chequered past with isosynchronous USB - various kernel version break/fix it.
(basically the BCM2837 used by rPI/Norns was not designed for this apparently, so its all a it of a hack)
unfortunately, that means, whilst its worth a punt with a rPI, I cannot tell you if it’s going to work on the Norns or not.