simonkemper

We spend a lot time on software development with max/msp and c in order to provide better support for our "evo" masterkeyboard with touch sensitive keys. Goal was to have a synthesizer which natively supports our high res protocol we are using in the evo.

Btw, the evo is a keyboard using capacitive sensors inside every single key to record the finger movement on top of a keys surface. With this we add another dimension of polyphonic input to a single key. Next to pitch and velocity there is now another layer of polyphonic data input.

The evo is backward compatible to midi. You can map the key surface to poly-at or simple midi-cc messages. Also you can make some nice stuff were every note is send out on a different midi channel in order to add polyphonic expression to synthesizers which normally don't support that.

And for a better integration we developed our own externals in c which communicate with the evos ethernet interface - this is needed because the evo is producing high res data at high speeds - much more than midi can handle -

All in all the externals simply add the evo to your patchers. There is no need to have knowledge about networks, ip addresses and so on. It is simply no configuration needed.

Well if this sounds interesting for you then check out our website -> www.endeavour.de

All the software, the max patchters and the externals are available there for free and are released under an open source license.

The external is compiled for both mac and windows (10.6 & win xp - till current versions)

If you like it just forward it to others,

PS.: special thanks to mr. Peter McCulloch for providing his perfect sounding moogish-Filter interpretation using gen... We are using that inside our standalone software synths.

We spend a lot time on software development with max/msp and c in order to provide better support for our "evo" masterkeyboard with touch sensitive keys. Goal was to have a synthesizer which natively supports our high res protocol we are using in the evo. 

And for a better integration we developed our own externals in c which communicate with the evos ethernet interface - this is needed because the evo is producing high res data at high speeds - much more than midi can handle - 

PS.: special thanks to mr. Peter McCulloch for providing his perfect sounding moogish-Filter interpretation using gen... We are using that inside our standalone software synths.


[share] - external and synthesizers/tools for our touchsensitive keyboard