Kind of seems counterproductive- the whole purpose of the E-RM is to provide a stable jitter free clock. You realizeany time you are filtering midi data you are introducing latency. The solid merging also means I can do simple stuff like send a clock to a sequencer and also have a controller send MIDI notes to it and the MRCC merges them nicely and I don't need to route the clock through the controller. Have not had any issues getting clock to only the devices that need it. The E-RM is sending a clock out to each patchbay and I have the MRCCs connected via their Remote 7 port to make them look like one big 12 x 24 patchbay I use port 1 on each MRCC to connect to the Sycologic.
#ERM MULTICLOCK AMAZON PLUS#
In addition to being able to route things, the filtering per route and per port gives you a lot of flexibility.īecause of the number of devices with MIDI inputs here, I'm currently using two MRCCs plus the older Sycologic M16 MIDI patchbay.
Sigh.Īnybody having better luck? Anything with user presets that are easy to set up and toggle through?Ĭonductive Labs MRCC here. So, as it relates to the Multiclock, one can only effectively send a single clock stream to all outputs- there is no way of sending one stream to some, and another to others. I recently bought a Motu Midi Express XT, but it turns out that beat clocks are automatically distributed to all outputs, regardless of in/out routings. Is anybody using a midi patchbay with their ERM Multiclock, and if so, which one?
0 kommentar(er)
