07-30-2024, 01:41 PM
(07-24-2024, 07:59 PM)Royce Wrote: I was wondering if you can try to put 'space" between the blocks of data you are sending.
The synth editor/librarians I use do not allow this.
The following is quite long so...
To summarize -
The PC->MRCC USB virtual MIDI cables solve most sysex dump routing issues.
But...
Even with a 1:1 routing, the Remote 7 will only pass a large sysex dump sourced from a PC In virtual cable. Routing the DIN inputs will not work.
Again, with just a 1:1 routing, the XpandR 4x1 will only pass a large sysex dump in 4->1 MIDI-DIN 'merge' mode (red led). Forget about using the 4 port USB 'expander' mode (blue LED).
Most of my sysex dump issues have been solved by using the twelve PC In virtual MIDI cables on the MRCC. One for each editor/librarian. These seem to be more reliable when patched to multiple MRCC outputs. There may still be some data loss, but dumps not failing and timing out, like before.
There are other major sysex issues, though, with the Remote 7 and XpandR 4x1 modules. I could not initially get the 'Trinitro' Trinity editor to send or receive PCG sysex dumps. These are sizable multi-bank sysex files, and a real test for the MRCC. The Trinity is routed through the Remote 7 outbound, and the XpandR 4x1 inbound.
I should say first that a directly cabled RME UFX II to Trinity two-way MIDI connection has absolutely no issues at all with PCG sysex dumps. Each MRCC routing was then tested individually to isolate what was causing the dumps to fail.
MRCC MIDI DIN In 1 routed to Remote 7 DIN out 3, with a simple 1:1 routing, cannot pass PCG sysex dumps to the Trinity. It fails every time, about 3/4's through part 2 (of 6) of the dump. For the test, the return Trinity to PC MIDI connection was a direct physical cable to the RME.
However, if the MRCC routing source is changed over from a DIN in socket to a PC USB virtual MIDI in, the PCG sysex dump though the Remote 7 will work properly with no errors.
But, there is more....
The XpandR 4x1, in expander mode with the solid blue LED, cannot pass a requested PCG sysex dump, back from the Trinity to Trinitro, even with just a 1:1 routing through the MRCC. IIRC, it instantly fails. For the test, the outbound MIDI was a direct RME to Trinity physical MIDI cable, to rule out the MRCC.
However, if the XpandR 4x1 is changed over to 4->1 MIDI merger mode, with the red status LED, and connected to an MRCC DIN input, the retrieved PCG dump will pass successfully.
The problem for me is that XpandR 4x1 is way too expensive to be acting as a basic 4->1 MIDI DIN merge unit. I will keep for now, to see if it will get fixed.
All the tests happened yesterday, and my memory is a little fuzzy. But, I can do more tests if needed.
............
More detail on my set up. The MRCC is used just for the subset of hardware synths that need sysex librarian/editor control, and excluding those synths that work with CTRLR-based VST plugin editors. The MRCC is augmented with the Remote 7 and XpandR 4x1 modules.
There are ten synths being routed through the MRCC, plus an Electra One Controller also patched in.
DAW traffic, (non-SYSEX MIDI), uses the two RME UFX II MIDI DIN outs.
RME MIDI Out 1 --> MRCC MIDI In 1, and routed to:
MIDI Out 9 - DSS-1
Remote 7 outs 1-4 for SY77, TG77, Trinity, CZ-1.
RME MIDI Out 2 --> MRCC MIDI IN 2, and routed to:
MIDI Outs 5 - D-550, 6 - K4r, 7 - Microwave, 8 - ESQ-1, 10 - AN1X
MRCC MIDI DIN I/O 3 & 4 give two-way connection to MIDI I/O 1 & 2 on the Electra One.
A Unitor 8 in standalone mode, merges the returns from from the D-550, K4r, Microwave, ESQ1, AN1X, before passing to a DIN input on the MRCC.