I can see the attraction for a very simple editor.
it would be really useful, when you just wanted to do quick midi mapping to vst or something.
(hmm, a vst is a bad example, since if Im at the computer - its no issue to use the editor!)
however, the more complex it becomes, the less Id likely use it.
e.g. I really cannot see myself typing names onto the screen.
at that point, it’ be easier to just connect the existing (chrome) editor and use my computer mouse/keyboard.
in that simplistic sense, I could see perhaps the following workflow:
- allow user to duplicate a preset on the E1
- I would then create a set of ‘templates’ (in current editor) , I use for these ‘quick edits’
- so, I select template , duplicate, then open it (on e1)
- place in ‘learn mode’ allows me to select each component, and do midi learn - to reassign CC.
(it would also be handy to have the ability to alter midi channel/port of a device, which is also another feature request.)
with this, Id be able to do quick maps, and carry on making music.
LATER… I’d like to load up the (chrome) editor, and download this new preset, where I would use the editor to edit names of components, and perhaps preset name.
sure this cannot cover 100% needs, but probably 90% can be done with midi learn. the next 10% gets complex (imho), e.g. adding options, renaming components, moving layouts - adding each of these takes more dev time and has diminishing returns for the majority of users.
so I’d keep it simple on the E1, and simple re-mapping that allows us to continue to make music. (without having to resort to a computer) BUT it leverages the existing (computer) editor for more complex tasks.
I like this approach on other hardware too…
e.g. sampler, I just want to capture new samples in the hardware, and use them immediately.
but I rarely bother renaming, and never start organising the on the hardware - when its just so much quicker/more comfortable to do on a computer (later in the day)