Its taken a while since v4.0 was released, but I finally just got to try out the new Remote Knobs feature with my wonderful new Faderpunk 16x slider controller. Easy to wire up MIDI out from the Faderpunk to one of the MIDI ins on the E1, and used the beta.electra.one site to set up the remote knobs configuration and routing. Moving the Faderpunk faders then moved the remote-controlled E1 controls (the first row of 6 controls), it works beautifully with my VCVRack preset.
BUT - if I switch module or change page so that the E1 control values change, then move a mapped Faderpunk slider, the E1 control immediately jumps to the incoming MIDI CC from the Faderpunk. This has various undesirable effects on the instrument (in this case a VCCRack patch) under control.
So, this is a request to please add an optional soft takeover feature to the Remote Knobs control algo to prevent these discontinuities happening when using a fixed MIDI CC source (non-motorised MIDI slider or MIDI potentiometer etc). Also, it would be very useful UX if the E1 display showed the position of the remote knob CC value vs the value of the control, so you can see where you need to move the pot or fader before you can take over the movement again.
There are some good examples on existing MIDI controllers for UX to show the position of the actual incoming MIDI CC vs the position of the control, so you can see where you need to move the pot or fader before you can take over the movement again. Here’s how the 4ms Metamodule shows the physical position of its control knobs vs the logical value of the controlleed parameter for its “knob pickup mode”:
Sounds like you have a similar experience with remote knobs as I have.
Only in my case when I change a page or a patch is being parsed on the E1, the remote controllers (an old Beheringen BCR2000) doesn’t follow along.
@martin , I know you couldn’t reproduce my issue. Is there anything we can do to help you out on resolving this?
Hi, it is fixed. I am currently testing the release. The Remote knobs now reflect (and send out cc messages) upon any change including the patch responses, Lua updates, snapshot recalls.
I like the idea. Not for the upcoming release but I added it to my TODO list.
I am wondering whether an “adaptive / scaled takeover” algo would work better than the current jump takeover behaviour, especially because of the lack of immediate feedback where the “target” value is in relation to the physical position of the external MIDI control (e.g. a fader). ie where the controlled E1 control in the matching slot increases/decreases its Parameter value proportional to the difference between the physical MIDI control’s value and the latched target value.
Once the physical MIDI control reaches MIDI value 0 or 127 (for 7-bit control), the external MIDI control and controlled E1 value then move directly in sync.
With this, the E1’s parameter value will always immediately decrease/increase in the same direction as the physical fader/ knob movement.
Sequential synths (and others) typically provide those options, and they make much sense.
They make sense for remote knobs too, especially if the remote controller is not responsive to MIDI CC input.
When the remote controller has encoders and LED rings, at first sight such algorithms are not really needed. But, if for whatever reason the remote controller goes out of sync versus the E1 ( which is currently the case when changing pages on the E1) , such adaptive or scaled takeover could ease out the consequences.
