Hello,
I don’t want to be pessimistic or whatever, but I am wondering what would happen if someday the company fails. Since the app is online, there would be no way to keep using the E1 as we do today.
Maybe it already exists (sorry if it’s the case), but I think that an offline installer would be a great addition to the sustainability of the product.
What do you think?
All the software and firmware is openly available on GitHub: electraone (ElectraOne) · GitHub
Thank you very much Moss. This is very good news. Maybe that link should be present in the official documentation?
But seemingly only for the mk1, or am I missing something?
It will be available for mk2 too. I just need to get rid of Renesas software source code bits before I can make it open source. I keep myself busy with working on that.
You have my sympathies–code cleanup just isn’t that much fun. 
Thanks for your efforts!
i understood the original poster meant the web app to manage and upload presets, not mainly the firmware.
I did not find that on github - did i miss something?
(actually very great, I didn’t even know the software is open source! 
)
Here you go.
yes, i know that address. it’s the first link posted at the start of this thread
there are many repositories, firmware etc., but none that I identifies as the web app for managing the device and presets as the original poster asked for.
There is something called “midi controller” - but from the readme I dont really understand what it does and how to build it, for which OS it will work etc.
Is that a management app? Can I build and run it on Linux or do I have to use it on Mac?
Hi,
the web editor application lives in a private repository. It is not a simple editor application, it also implements the cloud storage of presets, user accounts, etc. We are not planning to make that opensource. We are, however, working on a new version that can be bundled as an ElectronJS app and that will handle both online and offline operation. The alpha version for testing, providing limited functionality, will be available rather soon.
Note, our preset editor application uses SysEx calls and JSON API as it is described at https://docs.electra.one/. There’s no extra magic behind that. Anybody may want to experiment with that.
Martin
One and a half years have passed since this last post. Is there any update on the availability of an editor that can also be used offline? I completely agree that there needs to be a way to edit presets independently of the Electra One server. Thanks!
It’s still on the to-do list, but given our time and resources, priority is being given to other, more in-demand features.
Thank you for the update. I hope it doesn’t get pushed too far back on the priority list.
The github-Repository seems to have been cleared out/permissions changed:
Is this by design, and has there been any communication regarding the closing up? (I searched both on the website and the forum, and could not find anything; some official documentation is even still pointing towards now hidden/gone documents).
Yes, I did that last week because I want to do some maintenance to everything that was available on github.
what is to be expected:
following @jhh all Electra One related repositories will most likely move to codeberg.com
the firmware for Electra One mk1, that already was an opensource, is will be cleaned up, annotated, and will come back with an opensource license in Q2 2026. It will come along with the last update from me. Being an opensource everybody will be free to clone / fork it. I, as a maintainer of the original repo, will process pull requests on that (original) repo.
the (very old) ElectraOne Console app, that was an opensource already, will be updated to support mk2, and will be made availble as an opensource application again. It is a native JUCE based app that allows users to flash the firmware, observe logs, and fetch basic info from the controller. By definition, this application can be used as a reference design for anything that communicates with the Electra One - the SysEx protocol is implemented there. Planning to do this in Q2.
Now the big thing, Electra One mk2 and Mini firmware will go opensource before the end of 2026. The main issue why it was not opensource from the very beginning is that the source code consists of parts that prevent using an opensource license (Renesas HAL and ThreadX). I did, however, got rid of the HAL parts that are important for E1 users already. I will now migrate the firmware from ThreadX to FreeRTOS. My deadline is to make it opensource before the end of 2026. The reason is that the project simply grew too big to be maintained only by me. I am becoming the limiting factor here. Note, there still will be a compiled archive (.a) with true low-level stuff. Rewriting this would take simply too long.
The web editor will be split into two parts - an online library of shared presets and a preset editor. The preset editor part will be opensourced and adjusted to run as an electron application with an option edit local files. I can already run the editor as an electron app now, but I still want to have an extra time to finalize it. I expect it to be done before the end of 2026 along with the work on the firmware. The online library will be moved from google firebase to something less bigtech.
hw programming:
Important note, none of above will affect the web service as we know it now. And I will keep working on the mk2 firmware as I have done so far.
Thanks for your detailed explanation.
This sounds great, and I wish you all the best for the above plans (I’m especially excited for the firmware and the preset editor going Open Source).
Indeed that is great news.
