Forum

Here's a demo of my current eigenharp project:
http://www.youtube.com/watch?v=8zkuyYnD5kE

(Apologies to the poor folks in my friends/circles on FB/G+ who are going to get this three times over..)

This is a setup built from scratch in EigenD 2.0.44-experimental, with the keyboard hooked directly to an osc output agent. That goes to an 80 line python script that finds the maximum pressure / pitch bend signal across the keyboard, and then spits out a light pattern over HTTP that goes back into eigenD through the illuminator agent.

Very nice idea!!

I was wondering why you opted to use OSC and the Illuminator agent. Giving your technical skills, I think that writing a dedicated Python agent, probably using the Illuminator as a basis, would have been less work and easier to set up?

I think that's the next thing I'll try. I wanted to fiddle with the osc agent as well, just to ensure I knew how to catch its output.

The illuminator agent has a key input port, but does it have inputs for the other data streams? I'd need to bolt on a few more inputs for pressure, roll and yaw etc (although I guess that'll be easier than adding say the breath pipe to the osc agent).

All things being well. It only works in 2.0.44 (which seems rock solid while actually playing, but still prone to falling over when building new stuff in workbench and), and you have to be careful to decimate the data enough otherwise it can start to impact performance.

Maybe that's another reason to internalise it in the illuminator (or a copy) since then the eigenD threading system can more aggressively throttle back the light show rather than relying on the OS scheduler throttling back the external python interpreter.