yeah… so this all got put on hold…and its not really started up again.
why? well, historic really…
I first did an Orac integration prior to the firmware being open source, basically by re-write a preset, took quite a bit of effort, but was a bit slow - due to the amount of sysex the was going back n’ forth.
so I then re-wrote it all when we could write our own firmware.again a lot of effort and it did work really well… and was what I showed above, and had intended to release.
BUT then the e1 firmware was updated (for good reasons, and it was much better) but it would require a lot of big changes to this work again… and also I was waiting of the e1 firmware to ‘stabilise’
and honestly , I just didn’t have the energy to ‘re-write’ for a third time 
esp. as Ive got a load of other projects on my plate, and not been doing much with Orac of late, so its kind of ended up on the back burner.
the source code is available, and I guess it kind of builds (though I dont have time to support it)
basically it two parts…
a) custom firmware
I think its the v1 branch, as I think v2, was kind of a start to move towards the later firmware?
(though, it has moved on again since then)
b) MEC
so MEC is the application that runs on the Organelle (or whatever e.g. rPI) that sends the necessary data to the E1 ( using a custom protocol) - I think its on the electraone.1 branch.
(I’d have to double check these branches etc… as its been a while 
)
@NewIgnis its custom firmware, so I ‘manually’ draw these elements on to the screen.
so when I did this the firmware api was very low level, so things like parameter display was all part of the ‘midi app’, so I had to do it myself, along with things like ‘window handling’.
I believe this is where the v2 api is much richer… and so ironically, would make writing this part of my firmware much easier… but of course, involves re-writing it all to make use of it… which is where I kind of lost the energy.
