I’m aware that the hardworking E1 team is currently very busy. Days could probably have 72 hours or more – at least temporarily. I’m truly impressed with the E1 Mini. Nevertheless, I’d like to share some suggestions for improvements I’d like to see.
Below, I’ll share my initial ideas for future E1 Mini updates.
A) The values for the new “Rotary Knob” control type could be displayed in the center of the control.
I would like flexible assignment of the label fields. One option would be the current default setting (A). Alternatively, larger values (with more than four digits) could be displayed for the dial type controls below (B).
C) I would greatly appreciate it if the „PAD TOGGLE” control type could be assigned to the switching function of the controller knobs in addition to the rotary function, without requiring Lua programming.
I like the idea and I will try to implement it. It will need some thinking because it introduces something new that current project/preset structure does not support and there are several ways how to go about that.
But as I said in the beginning of the message, I like the idea and will try to make it happen.
Apologies if I missed or duplicating from other discussions - know you guys have been burning the midinight lamp but some additional ideas on the topic after using my Mini ~week:
Ability to show a constant / string in Group Label (e.g. show current MIDI channel)
Edit of V-fader labels
Page reordering (drag/drop in editor)
Page copy/paste across presets
Set colors with hexadecimal (match DAW / Instrument colors)
Device sleep after xx hour(s)
For what their worth… I’m already more productive with my Mini as is, so none of the above has any urgency.
This is so much more important on the mini since you really need multiple value controls that easily expand to compensate for the smaller display, fewer knobs, etc.
Since we are currently discussing the V-Fader controls, I think it would be useful to be able to assign different MIDI channels to the individual faders.
The main reason has been backward compatibility. The original preset format keeps the MIDI device at the control level. The reason is that at the time of designing the original JSON we did not imagine we could ever do something like an envelope with messages spread across several MIDI devices. Also, at that time mk1 featured 256kB RAM - we tried to optimize every single bit and byte. Things have changed and especially now, with vertical faders introduced, it totally makes sense to make it possible to define the MIDI device on the value-message level. I will - most likely - do that so that both control level and value-message level MIDI devices will be supported in the same time, with the value-message taking higher priority in the new firmware. And old firmwares quietly ignoring these. Or something like that.
The very same counts for the labels. So far, each control type has fixed set of labels such as attack, decay, … I will change it so that these are free to edit.
