Can sysex be made to pass thru the E1?
Other wise you need a midi merge box with 3 ins feeding the synth you want to control.
1 for the E1 output, 2nd for the sequencer input and 3rd for passing sysex patches from the computer.
if the E1 could pass sysex for patches from the computer then a lot of un/plugging midi cables could be saved.
Maybe you could use something like Midi Lab to avoid the Hardware (Midi Merge box)
http://en.soundigy.com/midilab.php
Yes, Electra does pass sysex messages (and other midi messages) by default. Anything send to USB port Port 1 is forwarded to port MIDI I/O 1, port 2 works in the same way. And it works in both directions, you can send sysex like this but also receive.
I ran into a weird problem, where electra is adding “line-breaks” to the sysex data. Every 32 bytes there is a F7 added. Is this normal? The sysex dump comes from a Prophet VS.
here is it captured with a motu midi express and with the electra.
| 00:41:39.967 | From Electra Controller Electra Port 2 | SysEx | F0 01 0A 00 0E 0C 0D 01 00 03 04 06 00 00 00 00 00 00 00 0C 03 08 05 05 02 00 00 05 00 08 03 01 F7 | |
|---|---|---|---|---|
| 00:41:39.990 | From Electra Controller Electra Port 2 | Invalid | 00 0D 01 01 05 09 00 0D 02 05 01 0C 07 02 09 00 08 00 00 00 06 09 05 07 00 0B 0A 08 06 03 07 0C 0C F7 | |
| 00:41:40.011 | From Electra Controller Electra Port 2 | Invalid | 00 04 00 00 00 00 01 04 09 0C 03 0E 0B 0E 09 07 06 0E 04 0C 0D 07 0B 0F 0A 0D 0D 01 00 0A 00 07 02 F7 | |
| 00:41:40.032 | From Electra Controller Electra Port 2 | Invalid | 00 00 00 0F 00 00 01 04 09 00 00 01 0A 04 04 00 0F 0C 00 00 00 00 00 00 00 00 00 00 00 00 00 01 0A F7 | |
| 00:41:40.056 | From Electra Controller Electra Port 2 | Invalid | 00 04 0B 04 04 0E 0E 00 00 0E 0C 02 08 00 0D 09 0C 00 00 00 00 0C 00 0A 04 01 06 00 00 00 08 00 06 F7 | |
| 00:41:40.060 | From Electra Controller Electra Port 2 | Invalid | 00 00 00 02 06 06 0A 00 00 F7 |
|00:44:41.843|From Express 128 Port 8|SysEx||F0 01 0A 00 0E 0C 0D 01 00 03 04 06 00 00 00 00 00 00 00 0C 03 08 05 05 02 00 00 05 00 08 03 01 0D 01 01 05 09 00 0D 02 05 01 0C 07 02 09 00 08 00 00 00 06 09 05 07 00 0B 0A 08 06 03 07 0C 0C 04 00 00 00 00 01 04 09 0C 03 0E 0B 0E 09 07 06 0E 04 0C 0D 07 0B 0F 0A 0D 0D 01 00 0A 00 07 02 00 00 0F 00 00 01 04 09 00 00 01 0A 04 04 00 0F 0C 00 00 00 00 00 00 00 00 00 00 00 00 00 01 0A 04 0B 04 04 0E 0E 00 00 0E 0C 02 08 00 0D 09 0C 00 00 00 00 0C 00 0A 04 01 06 00 00 00 08 00 06 00 00 02 06 06 0A 00 00 F7|
Hi,
I am looking at it now. Just so that I understand.
This messages received with your MIDI Monitor from E1 USB interface (port 2). You have Prophet VS connected to MIDI IO 2 connectors on E1. MIDI IO is configured to forward to USB device. Is that correct?
And this is when you connect Prophet VS directly to Motu interface?
What version of the E1 firmware are you running?
That is correct. The midi cable from the VS goes into E1 Midi In and then via USB to MIDI-Monitor. I’m using E1 as a USB interface. Is the midi buffer very small and is dividing the message?
Thank you for looking into it.
The bigger problem with the VS is his weird implementation of NPRN. MSB and LSB are switch but as well the parameter select bytes are in reverse order. 
E1 forwards a stream of packets (midi bytes). There is basically no limit on forwarded messages. It must be something else. I just tried to forward 4kB messages (from MIDI IO → USB dev)
(note USB MIDI cable is a USB to MIDI IO converter. So, E1 received MIDI data via MIDI IO DIN)
I will keep looking at it and thinking what it could be.
