Not sure this is due to the beta version: I’m hooking up the old Behringer BCR2000 as remote buttons via DIN MIDI port 2. Bidirectional controls works but only with a workaround:
However when applied, only the direction BCR2000 => E1 works.
When looking at the settings on the E1 itself: Remote Knobs > Outgoing, the Parameter “Remote Oubound Interface” is on “Not assigned”.
After setting this to MIDI IO + Port 2 + Channel 16, bidirectional comms are established.
These settings seem to be retained in memory, as long as I do not apply any controller changes through the browser at which point they are lost on the E1.
However, when applying control changes via the touchscreen instead of via the encoder knobs, no signal is sent out to DIN MIDI port 2
Same with applying patch parsing or changing pages on the E1: the controls settings should be sent to the remote knobs to sync them.
I have my second MK2 unit I can try it on. Is the web editor issue mangling control numbers when move pages around fixed?
Will you also output a log message if you create a control that has a duplicate parameter number. This is a huge issue for me. Ideally a list of all controls with their parameter numbers would be great to see in a log (can you do that?) as a lot of my code screws up if you use the same parameter number on virtual controls - unexpected controls can fire on you in that case. Thanks
I am having problems with this one. I configured my E1 in the same way as you did and the Remote messages seem to be sent out just fine when I use the touch screen. Are you sure it does not work for you?
Other observation : a refresh issue. In this Reface preset Electra One App, there is an init pad (control 44) that is supposed to become hidden once applied. Only it doesn’t, until after you refreshed the page.
Another strange visibility issue: in the DAW mixer, I set the visibility of the device selector whenever the list of devices to select (ie its overlay) changes, and to hide it if the number of elements is 1 or less. But this does not work as intended: the control is only updated when switching pages, and is still shown even if it should be hidden because the list contains 0 or 1 element.
Ok, found the issue in the DAW mixer: apparently if a control is already visible, and c:setVisible(true) is executed, this is ignored - even if the overlay changed.
Some more details on the EnvelopeMIDI case: also here switching to the Performance page and back sets the visibility of the controls correctly. Interestingly enough, when pressing the page switch button (lower left) the two controls that should have been hidden actually show up highlighted, while the other controls are dimmed as the shoudl be.
I tried to reflect upon most of the feedback provided here. The 4.1.0 is out - more info can be found at Firmware v4.1.0 for mk2
here’s a few remarks to what was discussed here:
@Phommed Assignment of knobs. All buttons can be assigned now. Extra context help was added. The help text is shown when the learn function is armed. When Electra is in the Alt mode, touch on knobs fires user functions, ie. they are auto-assigned. I will - most likely add an on-screen graphics that will provide info about assignments when Alt is pressed.
@NewIgnis The page selection has been made more sensitive and the bottom bar with the preset name and the info text stays shown. The Outbound Remote - the issue is in the editor, I will work on that now.
@NewIgnis@jhh control visibility issues introduced in 4.0.2a were resolved
@jhh dimmed controls are dimmed less now Display brightness → I agree but making the change you propose represents more work. I will do that in the next release.
@rkram53 Electra will no report duplicate reference ids to the logger. I will make changes to the editor that a) duplicates will be prevented b} users will be able to edit reference ids
there was an issue with setVisible() caused by the fact that page controls are now in the container that is moved vertically depending on whether the pages list is shown at the top of the page. I guess it was two issues combined in your case then
And one extra remark I’d like to add: I really appreciate your help with testing and providing feedback. The project has grown quite large, and even though I’m trying to automate as much of the testing as possible and maintain checklists for manual tests, your help and feedback are truly invaluable.
As for the remote knobs
The remote controller responds when I turn a knob on the E1 or when the knobs on the E1 get set by parsing a patch
It does not respond when I change a page on the E1, or when another preset is loaded.
yes, that is correct. I need a little bit more time thinking time for this one. It makes sense but I need think:
about how to it would be combined with the idea of the soft takeover function
about how it affects whole system. So far, Remote knobs messages were sent where there was a change in a control value.
I am happy to hear any input from you on that - I guess what you are trying to achieve it to use BCR to with the E1 as the middle man? Feel free to open a new thread for that, it might be interesting to others too…
Display brightness → I agree but making the change you propose represents more work. I will do that in the next release.
- did find a bug in my own code though, that is now also fixed.