mrcc as replacement for midex

[ruud]

hi all,
im running an analog studio with about 50 synths and 15 drum machines. most are synced with midi clock to a pc running Cubase. The only way this setup stays in sync, is with a now very ancient Cubase version and the connected Steinberg Midex8. It runs all machines, whether ancient or new, in perfect clock sync. As soon as i try other midi interfaces or other DAWs, things turn into a big mess timing-wise.

Id love to upgrade this setup as its getting very old, but simply said, nothing else works as good as this, apart from my old Atari ST. I see the MRCC specifically aimed at larger setups like this. has anyone replaced their Midex with this interface? Or are there PC users (Win10) that have similar setups and have this working with the MRCC? I typically have 4-5 drum machines (both old and new, also via midi-din sync converters) and 5-10 synths running internal sequencers and/or arpeggiators at the same time, some being triggered or transposed via midi notes in cubase. im not running 100s of tracks, or enornous amounts of cc/sysex/aftertouch etc data, on the contrary.

thank you for any answers!

[Jesse Johannesen]

I don't have any experience with Cubase or Steinberg MIDIex, but the only issues I have seen with timing has been introduced by the DAW/ operating system /CPU load types of things. If you are simply hitting play on a DAW sending only MIDI, it's not likely to be an issue, but if you try and load 15 rompler VSTs while it's playing there is going to be some consequences. The MRCC is way under its overhead "CPU" limit in all but the most insane routing scenarios, I think we tested it in what we thought was going to be a taxing setup and it was literally idle for 90 percent of it's clock cycles.

Some things to consider though before deciding:
There is currently a maximum number of routings of 44, so it's not currently possible to have a preset where every input is routed to every output for instance.
The USB host ports work with about 85% of things we see thrown at them, nominally the device has to be class compliant, and occasionally things that say they are can be problematic, if you have a use case you aren't sure will work you can take a look at our compatibility tracker here:
https://conductivelabs.com/mrcc-usb-host...y-tracker/

Round-trip the MRCC doesn't add more than 3ms latency, meaning 1.5 from PC to output of MRCC, and another 1.5 back into MRCC input and back to the PC. We tested it for 24 hrs straight with little variation using MIDI Ox as a source.

If you need any more info before deciding feel free to hit me up at support@conductivelabs.com with any questions.
Jesse