The app.electra.one web application now provides a direct link to download the firmware and instructions on how to update the controller.
Version 4.0.0 is a major upgrade packed with new features. Everything was designed to be user-friendly and accessible without deep technical knowledge. Alongside the firmware release, the Electra One documentation at docs.electra.one has been updated to reflect all the changes in both the firmware and the web app.
The development was intense and the testing even more. Still, I’m sure some things slipped through. If you notice anything, please let me know. If you run into troubles with 4.0.0, it is safe to downgrade back to 3.6.1.
I’ve done my best to include feedback and requests collected over the time. There were a few features I hoped to include in 4.0.0, but I had to draw the line somewhere. Once things settle down and most users have moved over to 4.0.0, I’ll update the development plan to give you a and idea of what might be coming next.
EDIT: Some of the new features still need doing in the web editor (while they are fully implemented in the firmware). We are busy with that and we will release them as we go.
Thank you for making the best midi controller even better. I wonder if firmware v4.0.0 will allow me to make larger presets than before? Electra previously failed my attempt to make a preset for Behringer Deepmind 12 as you may remember.
Congratulations @martin for your perseverance and hard work over the past 12 months to get v4 over the finishing line . Love the new on-board settings and routing features (although I am also looking forward to watching your new video series so I can learn how to use them all to their fullest capabilities).
Yes, the firmware 4.0 does support multiple Lua files in a single preset. The feature was inspired by your work You can now divide your Lua script into one main executable file and several supporting modules. This is fully supported by the firmware. I’ll be adding support to the web editor very soon. I’ll reach out to you when I start working on it so we can use your preset to test everything and make sure it works as expected.
That sounds very exciting Previously when I was experiencing the limitations we tried to solve it by putting certain files on the SD card. It was difficult to keep track of which IDs were used so I stopped developing my preset for Deepmind 12. Does this happen automatically now?
It’s still early days in my Electra One adventures but I found myself copying the same sysex-related Lua helper functions from one preset to another and thinking it’d be so nice if one could just use a shared file somehow.
Martin - I read you as saying that if a problem should turn up using 4.0.0 (which is now successfully installed), a downgrade to 3.6.1 is a way out. Should I keep the 3.6.1 file in the boot folder, all the others (except 4.00.) can be removed?
Hi, what I meant is that if someone upgrades to version 4.0 and runs into issues they don’t like, it’s still possible to downgrade the controller back to version 3.6.1. Hopefully, that won’t be needed. Keeping the v3.6.1 firmware file in the boot folder would make the downgrade easier. So, I’d suggest keeping it there for now, you can always remove it later.
Congratulations! A couple of weeks ago I installed firmware-v4.0.0.srec (2025-04-07) from the beta site. Am I good or is the “stable” 4.0.0 more recent?
I have beta version 4.0.0srec and I tried to update from my browser, but the controller won’t update; it stays stuck on the “updating firmware” screen.
Is there anything special to do when updating from a beta version?
Thanks.
This issue is caused by the fact that your bootloader has not been updated yet (which is the case for most users). However, since you had the beta version installed, the website is offering an online update to the stock 4.0.0.
For now, ignore this message and the update button and update the firmware manually as you did before, ie. switch to bootloader mode, enable USB Disk mode, copy the 4.0.0 firmware file to the boot folder, restart the bootloader and tap the 4.0.0. If there is an update.srec file in the boot folder, delete it.
Let me know if it worked for you. The v4.0.0 firmware is available at downloads page.
Thanks! At one point, I had to test the links and files on the beta site as if they were in production. During that time, the beta site provided a beta firmware version that didn’t include the usual “beta” label in the version string. To make sure you have proper and official release, download the firmware file from downloads page and update once more. sorry.
multiple Lua files for one preset - to make the scripts easier to manage and organize
support for uploading / maintaining the shared preloaded Lua modules. To provide library style functionality, helpers, etc.
Shared modules: This has been around for some time but the only way to get the files (Lua modules) on to the controller was using the USB disk mode. eg. @jhh’s ableton script uses it. Now, the firmware supports uploads from the website. As mentioned above, I still need to add the feature to the website. Also, I will act as a maintainer of the namespaces (folders where users - developers will upload their modules) by creating those namespaces by myself upon contacting me. These official namespaces and the files in them will be distributed with the controller. More info on that will be provided later.
. Love the new on-board settings and routing features (although I am also looking forward to watching your new video series so I can learn how to use them all to their fullest capabilities).
You can now divide your Lua script into one main executable file and several supporting modules. This is fully supported by the firmware. I’ll be adding support to the web editor very soon. I’ll reach out to you when I start working on it so we can use your preset to test everything and make sure it works as expected.
Previously when I was experiencing the limitations we tried to solve it by putting certain files on the SD card. It was difficult to keep track of which IDs were used so I stopped developing my preset for Deepmind 12. Does this happen automatically now?