We have finally got to the point of preparing a new manufacturing batch. The unavailability of critical parts and experience learned in last three years resulted in designing an updated version of Electra One.
Electra One mkII is fully compatible with the original Electra One. The changes are under the hood. A new CPU and large memory expand capability of the controller. When we designed the original unit three years ago, it was really meant to be just a synth programmer. It was you - the users - who gave the direction to the project. Electra One mkII is designed to handle lot more MIDI traffic, run complex Lua scripts, and do all that much faster.
An important thing to mention: we keep the original Electra One fully supported. Whenever we come with a new feature, we will try to implement it for both makes, the original and mkII. Of course, sometimes it will not be possible.
And the most raving feature: the SD card will be accessible
Hi Martin, will the unit look the same? The same form factor?
Will the memory upgrade allow the e.one to be able to handle larger blocks of incoming sysex data?
Or will the MK1 also be able to deal with larger incoming data?
yes, I keep the same form factor. The size of the controller feels just right. An attempt to make it with 16 knobs resulted in bulky, ugly device.
What is on the drawing board, greatly inspired by input from @NewIgnis and by what I saw on @phonaak desk, is a docking station for Electra One, that would offer additional 24 pots, a set of extra buttons to switch pages, presets, modes. There would be also an extra narrow LCD and larger encoder. The docking station would also feature more USB ports and a power supply. I am about to make a few prototypes. I am not sure if and when it would be actually manufactured.
mk1 with firmware 3.0 and higher handles large SysEx messages. The difference between mk1 and mkII in this is that while mk1 stores larger SysEx messages in relatively slow external RAM (actually the unused part of the video RAM), mkII will do the work in SDRAM directly connected to the processor. It means much faster and without multiplexing data transfers with refreshing the graphics on the LCD.
I was away from my device and i get back and installed the new update. I was about to write something about how mutch the E1 is a mature midi controller regarding all the midi controller i had /have/know. Robust, autonomous, user friendly , useable for both beginner and Advanced people . Totaly customizable ! And the new firmware confort greatly my opinion … Am i FAN ?..yes . Then, wow ! A new version more powerfull with more controlled parameters ! That’s ! A ! GREAT ! NEWS !
After playing with the MKI the thing i would love to see on the MKII is to have the ability to control all the 24 “others” displayed parameters with an external controller connected to the E1 natively (without the need of lua of coding i mean ) . Touch screen is great for “macro” mouvement when you don’t need to be precise and i love to have to ability to use it but i clearly prefers pots, faders, buttons etc when i need to be precise . Touchscreen is great for X/Y or controlling one parameter with a big fader or for 0/127 buttons .
Thanks Martin ! That’s a great news ! . I buy one now !
PS : And the forum … My god ! such energy, knowledge,positivity and simplicity ! i love that ! Thanks to all the E1 World !!
PS 2 : I see i can ALREADY preorder it !!! !! That’s an awesome news then !!! … 5000 parameters !!! . I think i won’t need more …normaly…
I use 2 Intech Studio EN16 controllers as an addition to the E1.
If the encoders have RGB LEDs, it is much easier to identify which parameter they belong to. If the encoder is also a switch, it is very useful.