That’s good to know about the Mio10 / MioXL. That’s what I was thinking- so long as the filters and soft redirects don’t introduce jitter, and the latency is consistent, shouldn’t be a problem. So even if you introduce latent and don't correct for it, you have eliminated jitter which is much more problematic. But latency is not the point of the Multiclock eliminating jitter is. Just need to wrap my head around what else might work for this tangle of gear…Īlso regarding latency, the Multiclock can compensate. That said I’d like to make sure I’m going about things in the right way and avoid problems I haven’t yet encountered, and will abandon the quest for an all-in-one router/merger/filter/splitter if it’s a foolish one. I haven’t run into any issue running a few of its outputs through a smaller patchbay (midihub) that’s also sending/filtering other midi data, but at the same time I’m only testing a single scenario and am probably not using it to its fullest extent- I’m not yet integrating it with a DAW- I’m just getting a few sequencers in lock-step with one another, and for that it’s working perfectly. The idea being that the Multiclock outputs would be routed differently based on a small set of instrument configurations. The appeal for using a patchbay is to have an all-in-one merger/router/filter/distributor for a rather large system that’s being shared with someone, to make it easy to toggle between presets that handle everything other than the ERM’s internal channel presets (unless that’s addressable too!). Same with most modern MIDI patchbays - lots of Ins and Outs so you can set up routes without chaining devices or needing lots of complicated filtering. It's there to solve problems if necessary, but not a required operation. Since you can target specific devices for reception, you typically don't need to filter a lot on the MRCC. Running the E-RM through the MRCC so that multiple devices can get the same clock is going to provide all devices with the same minimal added latency. The Sycologic does no filtering/merging/re-routing/channeling it's just a patcher without a CPU in the way. That's part of the reason why I moved from the JL Cooper Synapses to the Sycologic. I'm very familiar with MIDI filtering and what it does. Without the quote, not sure which previous post is the target for this comment. 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. 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |