Exactly what I was thinking 
This all sounds very interesting, but also quite complex.
I’m possibly the only member of the “keep it simple” faction in this forum. Personally, I much prefer to tackle the simpler steps before the more complex ones.
For example as I mentioned before, I would greatly appreciate it if the switching function of the knobs could be easily assigned to a pad function, in parallel with the dials, faders, etc., without having to write any Lua code.
The V-Faders are great. I’ve tried using them. But unless I’ve overlooked something, they’re only useful when sending on a single MIDI channel for an instrument. Since I’m working on a preset for a kind of dawless jam with the SEQTRAK, I often only need one, two or three controls per part (= MIDI channel). Therefore, they’re not very helpful for a MIDI multitimbral instrument, especially since they occupy the entire screen, preventing simultaneous access to other controls. They also don’t display values, although that possibly might not be the final version.
Hi @martin , just fired up my E1 Mini (on FW4.1.2) for the first time and playing with its new functions.
One issue I noticed on the initial “Demo Preset” (which has four extra mapped buttons):
- Select the “Context” action
- Repeatedly press the “Randomize” button. Sometimes, the state of the four preset buttons get toggled by the randomizer, which seems to cause the buttons to be rendered over the top of the “Context” buttons.
- This confused me until I realised what was happening, because the Context button actions still worked, although the rendered buttons were showing the preset’s buttons.
I would suggest that if the randomizer (or any other change e.g. incoming mapped MIDI message that affects those buttons) does not re-render any of the four bottom preset buttons if the Context menu is open. Also maybe change the state of the Context button to show that its buttons are active. I don’t actually know what the intended UX is, to be honest.
It might also be useful to be able to disable any preset control from being affected by the Randomize function e.g. probably do not want a mapped “Start” or “Stop” transport button to be toggled on or off.
I managed to set up the Mini as a “Remote” to my E1, once I figured out the routing, it seems to work as intended, including the E1 → Mini “Outgoing” feedback. This is the first time I’ve played with that feature, nice! Have some immediate thoughts on how it could be improved further, will post in a different thread about those at some point soon.
I already noticed that one too and have that on my todo list.
yes, currently the randomizer (on both models) is a true hard random for all preset controls. I agree that some way of excluding certain controls would be useful - either automatically or by the users.
Hi @HaPe , display page works in the last version. I used it in the Evil Pet preset for Mini
1 Like
Hi @NewIgnis,
Thanks a lot for letting me know. I’ll check it as soon as I have the chance to get my hands back on it.
Have a nice evening.
1 Like