So I’m trying to make a EO Mini preset for my AlphaJuno1, using Midi Learn. Strangely, sometimes it works, sometimes nothing happens and it keeps waiting for a signal. That’s question (or annoyance) #1. (I recently succeeded mapping my AlphaJuno to the Behringer BCR2000, without a problem - so the Alpha sends out sysex correctly, that’s for sure.)
#2: I succeeded in ‘learning’ my Mini the Alpha’s DCO Range, which ranges from 0-3, but it captured 3 as a ‘Constant byte’, thus as a fixed value. I can change this into a ‘Value’, but why doesn’t it do this automatically? (I retried ‘learning’ DCO Range, again, just to make sure #1 isn’t parameter related, and now it doesn’t work - the editor just keeps waiting till I send a value while I’m turning the Alpha dial left and right till eternity.)
#3: As shown on the screengrab below, the X for closing the sysex edit screen overlaps the X for closing the editor, on my 15 inch Acer laptop. I can’t close the sysex screen without closing the editor.
#4: Yesterday I had the Cutoff working. When copying the knob and changing the sysex to enable Resonance (sysex F0 41 36 0F 23 20 01 11 value F7 instead of F0 41 36 0F 23 20 01 10 value F7), both knobs moved simultaneously. What did I do wrong? Of course I don’t mind using Midi Learn parameter by parameter, but as described in #1…
Thanks in advance!
PS. I’m not a coder, and prefer using the drag and drop web UI for the Mini.
Please let me know where I can find this documentation - thus specifically for the Mini, specifically for using Midi Learn. I could only find docs for the Mk1. Thanks.
I’ve recently finished a preset for the Alph Junon 1 for the Mk2.
I know that doesn’t answer your questions, but I might provide you a basis for a Mini preset.
The first page is the most important.
Be aware the preset also contains an additonal LFO not present on the Juno itself, and that, when performing a program change on the Juno, the preset parses the parameters.
Thanks, I already had a look at it and couldn’t figure out the code - way to complicated for me. Impressive! But do I understand correctly that the Electra One can also be used to read values, instead of just sending them? Hope this is possible on the Mini as well (it has Midi In) and more so, that I can get this working with the web UI.
The problem seems Sysex related. I just tried Midi Learn with my Minilogues CC and it works great.
@martin , can I ask you to give your view on this (see my first message, above)? Might this be fixed in the recently announced Mini FW update? In short: I’d like to use Midi Learn on my Electra One Mini on synths that (only) send out sysex, like my AlphaJuno1.
yes of course : I don’t believe Midi Learn will work with SysEx. SysEx is System Exlusive : every manufacturer uses its own conventions, so there is no way a device could reliably tell how to ‘read’ sysex. That must be programmed.
NRPN, RPN and CC are standard messages though, here MIDI values are learnable
Electra’s MIDI learn does support sysex messages. If only one sysex message is received, it will result in a string of constant bytes. If multiple messages are received and only one byte is changing, it will interpret that byte as the parameter value. like this:
If more complex messages are coming in or if several sysex messages with different byte structures are coming in during one sysex midi learn session, the controller might get confused and some handholding is required. I expect that something like that might be happening in your case. Can you check with the MIDI console (in the web app) what messages are coming in from your AlphaJuno?
Thanks @martin , I solved it by manually entering the sysex string. A Electra One Mini preset for the AlphaJuno is on the way (As well as a Matrix-1000, a VX-90 and a SX-240 one!)
(As well as a Matrix-1000, a VX-90 and a SX-240 one!)