Would it also be possible for fw 3 too (optional), so that after pressing the lower right button once (not holding it down), the “page select” menu should be visible on the display until I select a page?
So that I don’t need to hold down the button?
Now I can’t switch to page 1, 2, 3, 7, 8 not so good with one hand, because my hand touches the encoder of page 12.
I play the bass guitar, so I need to be able to switch pages quickly with one hand even in “live”.
1 Like
Of course I wanted to reply to Martin.
I need the option to set that in the case of a E1 parameter, if the controller poti is at a different value than the controlled parameter and I move the controller poti, then the value of the parameter does not immediately jump to the poti value, but waits until the the value of poti reaches the value of the parameter and then changes from there. I control the parameters in E1 from several sources, and unfortunately the midi communication is not two-way. if the first controllerer sets a value, the second controller “doesn’t see this” “of course”. then if I want to control the same parameter on the second controller and move the pot, the value of the controlled parameter jumps to zero, which is very bad unfortunately.
what I ended up doing in some cases was to “use up” a slot in the lower right corner of two pages and placed a momentary pad that simply switched to the other page. That gives me a quick way to toggle between two pages.
Not a solution for multiple sets of pages, but it does give me a single quick press way to toggle.
Using LUA, you can do this. Set up a virtual fader/list. Save off the value when it changes. Next time to control is touched, allow the user to change it and only send the parameter (using a midi.sendNote() or similar) after the saved value has been seen again.
The coding to make that happen will take a bit of thought, but it definitely can be done. Whether that’s something you want to undertake to solve your problem for all controls or not, I don’t know.
1 Like
I use all pages in a preset and all “parameter” on a display.
there should be some kind of solution or setting option that can easily solve this, because all the parameters that I control are “like this”, controlled from several sources.
Think about it from the E1 view.
Every time a control is touched, it sends a value by default unless it’s a virtual control. In that case, you have some determination over what it does. Depending on the kind of control, different types of MIDI messages are generated and sent. Also, the value of a message may be a note on/off, a value from a list, or some range of MIDI values.
To be able to implement a “pass-through” mode (which is what you’re asking for like on some synthesizers), every control would have to save the last value, indicate that value on the display some how and then wait for a user to move the control through that value.
For a single control on a single page, not too hard. For possibly 36 controls per page, that would require a lot of overhead to remember state, restore it when pages change, monitor the user movement and only send after a value has been reached, change it when controls get hidden or moved for an entire preset.
Again, not saying it cannot be done, but the overhead to support the possibility of doing that natively would seem to be a large use of resources that might be better applied elsewhere. Of course Martin has the final say. I tried this approach for some controls, but I found it easier in my case to pull back the sysex from the device and keep the E1 display reflecting the current value.
2 Likes
OK. I don’t understand the programming part at all, I write everything from the user’s point of view. I didn’t think it was so complicated to solve. I thought that such a simple setting option would not be complicated.
now that I know that what I want is not as simple as I thought… I can solve it by controlling only the very important parameters from 2 sources
could you make me please a preset that contains only what you wrote, how to solve it in the case of a fader? I haven’t worked with virtual messages yet.
I posted a public preset example. It is rough, it works for 2 controls, it uses LUA.
I tried to comment in the LUA as necessary.
If anyone wants to work on it to make it cleaner, more generic, feel free to improve it
The 2 pads on top show the saved values.
The 2 faders change what might be sent and then the pads update to show when you pass through the saved and what the new saved value is for that fader.
3 Likes
this is mostly for @NewIgnis and @oldgearguy…
I am working on the patch dump parsing editor now. The main goal is to make it possible to handle multiple responses to one patch request. I just released an updated version of the editor. Not perfect but a few things that were not possible, should be possible now. Please give it a test ride.
As a bonus, the new editor can be used for JSON now too:
5 Likes
looks amazing. The ability to more clearly see what’s going on and the mapping in the Patch Editor is very welcome.
Here in the US we’re approaching a holiday on Thursday and for me that means family in town and much non-music activities, so my initial time to test will be somewhat limited.
(my family doesn’t appreciate the incredible tool that the Electra One has become. 
)
1 Like
it is not meant to be an order to work enjoy the holidays!
1 Like
lol – You put a lot of effort into this so I didn’t want you to think I was just ignoring the update.
We’ll see what can be done.
2 Likes
Long names in categories trigger a horizontal bar on the screen, hiding the name
Multiselections are hard to see. Here VCO1, VCO2 and EXIT IN/FDBK are selected
It would be great if we could change some characteristics in one go for a multi-selection of controls, such as the category, the color (I love the color selection by the way!) and the visibility.
1 Like
Just to make sure… the actions on selected items have been added already: copy, cut, change colour, and remove. I will add a change of category. Visibility makes sense too, but possibly only if there is a lua script…
1 Like
Quick question for you folks that have been playing with the new colors -
Do the new ones have predefined names to use in scripts?
I was just going to make a color preset with a bunch of different pads, then look at the epr file to get the hex representations.
I’m excited to use the multiple sysex responses handling in my Ambika presets in the future 
Thanks for all your energy to make the E1 even more usable Martin!
1 Like
