the recent Firmware v4.0.0 for mkII - #20 by martin completes most of the functionality I originally wanted to have on E1. There are still a few additions I’d like to make within the 4.x firmware line. This post is meant to give you a quick overview of what I plan to work on next:
with the recent addition of the UI toolkit (forms, etc.), I’ll be adding an on-device preset editor. This will allow you to create and edit presets directly on E1.
users will be able to map preset specific actions/functions to hardware buttons.
the Captures feature will be extended to support recording of all MIDI data in the Standard MIDI File (SMF) format. Currently, only a single SysEx message per capture is supported. The update will also allow capturing messages generated by the controller itself, such as automation..
I will add a simple on-device method for routing output from one preset to another, e.g., sending LFO data (Data Pipe) from a modulation preset to a synth preset.
The router will be extended with functions to filter and remap messages.
A new control type for entering and editing texts (e.g. patch names) will be added.
I will extend the LUA API - it will be discussed in another thread.
I may also experiment with adding a network interface to Electra One. If successful, this could open the door for OSC support and even hosting the web editor directly on the device. I am not sure about those two yet though…
As for MIDI 2.0, the firmware is technically supports it, but I will hold off until there’s wider adoption of the standard by other devices.
There will be work done on mk1 Electra firmware done too.
Thanks Martin for the awesome v4 update, I’ve not had time to properly test it yet unfortunately but looking forward to.
I am loving how you are making the E1 more and more like the central midi control-hub for your studio. As more and more instruments, midi-routers and mergers are added, setups get more and more complicated to navigate and remember.
So I had an idea:
A page on the E1 that’s visual overview of the MIDI-routing in your studio, that the E1 is installed in? In the sense that you have boxes (like the “button” in the editor) representing equipment, with it’s I/O (MIDI & USB) and interconnections graphically represented. Maybe a possibility to add comments to the devices and as a “button-box” to attach information specific places along the routing map.
This way it’s easy to reference the midi-routing the E1 is used in, have a reference for where various splitters/mergers are located etc. I make documents but it’s not very intuitive nor immediate, and having it all viewable and saved in the E1 would be nice. I would imagine one could use the editor for most of this already, so maybe not so much work.
Hi Martin, I was wondering if it would be possible to implement the ability for the display to be turned upside down so that all pots would be then placed above the display ?
It would be much more comfortable in some cases (in terms of cabling and/or in terms of viewing angle).
Of course pot #1 would become pot #12, button #1 would become button #6, etc…
One could switch this orientation in the CONTROLLER/Configuration section of the site with a button for example.
Sorry if this has been discussed somewhere else before…
hmm, never thought about that And nobody has asked for such thing until now. I think I will not do that on standard Electra, I can imagine, however, considering such an option on Electra One Mini. It has a layout of buttons and knobs that is more friendly to that idea.
Ah OK, I would have thought this could be a rather simple addition because it doesn’t mess with the general complexity of the engine, just the display…
In eurorack land it happens that one installs a module upside down depending how it is more adequate to have cables up or down…
And nobody has asked for such thing until now. I think I will not do that on standard Electra, I can imagine, however, considering such an option on Electra One Mini. It has a layout of buttons and knobs that is more friendly to that idea.