it worked fine when I tried it … otherwise I wouldn’t have posted here 
the e1 firmware and toolchains can change, so its always possible that things become mis-aligned at times.
I’ve not been compiling the E1 code recently, as Ive been waiting for it to ‘settle down’ again. as it was going thru some pretty major changes, and didn’t want to have to keep updating my own source code to follow it.
Yeah, saw that there is a 3.0 coming. Before I really start investing time into the project, I wait until that is released.
The idea is to make the Midi Controller application (the one we all are using) just another application that runs on the base firmware foundation. When that point is reached, I will claim the base firmware to be mature enough for developing other apps. Many people are currently helping me to get things right, I think we are getting close to that point…
Is E1 still open source? The last commit at ElectraOne · GitHub is from 2024-09-09. I’m wondering if it’s a delay or a policy change.
The Electra One mk1 firmware is open source and we keep it that way. That is what you have seen on the github. Electra One mk2 was introduced at the time of the global electronic components shortage. At that time, we had to change the main CPU on a very short notice to be able to keep the project alive. To do so, we used Renesas SSP libraries in the mk2 firmware sources (the base USB stack, SDRAM, etc). These have proprietary license that does not allow us to simple share it on github,
We are getting rid of these libraries replacing them with our own implementation. Kind of step by step when there is time for that. But as there was almost no interest the firmware sources, we spend more time on improving the Lua API that allows building quite complex presets without modifying the base firmware.
People do care about source availability, even if they don’t actively contribute. Even as a purchase criteria, as it was for me.
Thanks for the explanation and good to hear it is being worked on 
There are always priorities and only so many days in a week 
Thanks for the explanation. That makes sense about licensing.
I found sd-4.0.zip, the preset library, and the API docs. I looked at the Lua code for your generative sequencer and the Ableton Live script by JHH. Yes, you can do a lot with the existing API!
It might be convenient to have: 1) the API source, with or without function implementations; 2) the docs in original .md form; 3) the web editor source.
In the end I’m not sure about a purchase. I only have one unit that really needs the 6x6 dispatch mode. However, I spent some time investigating so here is my feedback. I hope it helps!