Yes! Conductive Labs has updated The NDLR firmware many times since its introduction in 2019. The latest released firmware can be found on the Downloads page, along with the instructions for updating.
In addition, if you are a member of our user forums you will have access to pre-release versions of the firmware. The pre-release versions are posted to test specific fixes or enhancements prior to general release. Release notes for all releases can also be found on the forum.
Yes, you can connect 2 MRCC’s together and remotely route outputs!
This feature was added after MRCC started shipping, so it might require a firmware update. Get it from the Download section, or check the forums MRCC Open Beta Firmware section for pre-release firmware and release notes. You must be logged into the forums to see this.
When 2 MRCC’s are connected, the Y guy lights up in the top right corner of the screens of both MRCCs.
Route MIDI Outputs on the 2nd MRCC by holding the Remote routing button. It is left of the encoder, and marked with the Y guy. Press and hold the Remote routing button on each MRCC to see what remote outputs are routed from the selected Input port.
Save your settings on each MRCC to save the remote routings you created.
MRCC’s are connected using a CAT6a shielded Ethernet cable plugged into the RJ45 on the right side of the MRCC. The best kind of Ethernet cable has metal shrouded connectors that are connected to a drain wire in the cable. We have tested up to 32 feet (10 meters) with a CAT6a cable. You might be able to go longer, maybe up to 50′ with a good cable. A regular Ethernet cable might also work for shorter distances, like 6 to 10 feet. YMMV
The MRCC to MRCC electrical connection is not MIDI, but a high speed serial interface. The MRCC to MRCC cable does not factor into the MIDI spec cable length limit of 50 feet. Therefore, you can still use long MIDI cables on each MRCC.
The MRCC USB Host Ports are USB 2.0 specification compliant. These ports have over-current sensing protection circuits, which when tripped will remove power from the USB device that is connected to MRCC. When this happens the LED indicator next to that USB port turns an amber color (instead of green). This protects MRCC from being damaged by faulty USB devices.
Over-current protect can happen with USB devices that require an external power supply but do not have the power connected, or it is drawing more current on power-up than what the USB 2.0 specification allows.
If your device is triggering USB Host Port over-current protection:
- First turn off MRCC with the power switch. This resets the power protection circuit.
- Try using the external power source with your device, and turn it on before switching on MRCC.
- Switch on MRCC. A good USB connection will be indicated by a Green LED indicator next to the MRCC USB Host Port.
Yes, MRCC automatically routes MIDI clock from any input to any routed output, or multiple outputs.
When you don’t want the MIDI clock to route, such as when there is more than one clock, its easy to set up a clock filter. Just toggle the Clock filter (red clock icon below):
When using the MRCC MIDI clock, you choose which outputs to send the clock to while on the Extras -> MRCC Clock menu page. Press the output button for each output to send clock to, the LED will light red. When the MRCC clock is running, the input LEDs will blink in time with the BPM while on the Clock menu page.
The MRCC MIDI Clock can also be sent to a CV clock output (3.5MM jack). This is useful for syncing MIDI devices with modular or semi-modular synths. The CV clock out supports 5V and 12V outputs. It can be configured for 1, 2, 4 and 24 PPQ. Currently, the MRCC cannot send an external clock source to the CV clock out, but we plan to explore that for a future update.
Yes, but there are some limitations.
Currently you can route SysEx from any MRCC input to outputs 1 through 6 (5 pin DINs).
Outputs 7 through 12 do not have SysEx support at this time.
The Remote 7 will route SysEx when it is configured as MIDI thru for outputs 1 thru 5. This is currently the default.
Most vendors recommend connecting their MIDI devices directly to the computer for firmware updates.
The MRCC’s four USB 2.0 host ports are designed to support USB MIDI Class Compliant Devices. That is, USB MIDI devices that do not require a special driver to function. The USB host ports are designed to work best with USB MIDI controllers.
The host ports can also accommodate a standard USB keyboard for entering port labels.
At this time, the USB Host ports do not support a USB hub for expanding the number of ports. We plan to investigate adding hub support. Keep an eye on the MRCC user forum for announcements of firmware updates.
Check out the MRCC USB Host Port Compatibility Tracker for reported compatibility with specific devices.
One way to tell if the device is USB MIDI Class compliant or not; if you have to install a driver on Windows or Apple OS to use the device, then it’s probably not class compliant. However, there are exceptions. For instance, some Korg devices, like the nanoKontrol will use a driver that is required to configure the device, but also works fine as a USB MIDI device without the driver.
If you are having trouble with a device, please check with the vendor of the device to find out if it is supposed to be USB MIDI Class Compliant.
USB is a complex and timing sensitive interface. Some USB MIDI devices may pose problems for the MRCC USB host ports. Please report your experiences on the MRCC user forum. We will do our best to address compatibility issues, but cannot guarantee success with every device. Using the 5 pin DIN is always a good option if your device has it. Performance is the same whether using 5 pin DIN or USB on MRCC.
Yes, Rack Ears are available as an accessory. The MRCC is a 2U device and can be mounted in a standard 19″ rack with the optional Rack Ears.
The Remote 7 accessory for MRCC extends MIDI ports to where you need them in your studio, up to 50′ away, and adds 5 additional MIDI outputs!
The Remote 7 is connected to MRCC via an Ethernet cable. The cable is connected to MIDI outputs in the MRCC and those ports are connected to the Remote 7. The RJ45 ports are not Ethernet ports, do not connect Ethernet devices, it may damage the MRCC or your Ethernet device.
When the Remote 7 is connected to MRCC, the MRCC will detect and enable it.
The 3.5MM TRS ports are attached to Remote 7 ports 1 and 2. The 3.5MM port attached to Port 1 is an A type TRS MIDI (the format adopted in the MIDI specification, and used by Korg and others), and the 3.5MM port attached to Port 2 is a B type (as previously used by Arturia and others). Its safe to try both ports to see which works with your MIDI equipment. And both the 5 pin DIN and 3.5MM output attached to it can be used at the same time.
Upon initial release of the MRCC, the Remote 7 ports acted as “MIDI thru” for MRCC outputs 1 thru 5. As of firmware version 1.1.020, the Remote 7 can be configured as five additional individually routable ports configurable on Settings page 2. In the “Remote 1-5” mode, use the Remote button (marked with the Y guy to the left of the MRCC’s encoder). While holding that button down, select the output 1 thru 5 to route them. The LED for that outputs turns yellow. Hold the Remote button to see what Remote 7 outputs are routed.
MRCC and MRCC accessories are shipping now.
Yes! Conductive Labs will provide periodic firmware updates to add features or fix issues reported in our MRCC User Forums.
Yes, but it will severely limit your choices for carrier, and might cost more and take longer to deliver than an non-PO Box address.
Generally, orders made on conductivelabs.com shop require signature for delivery, but it depends on the carrier. Express carriers will require signature when the orders is of a certain value. While carriers that pass the parcel to the local postal service will typically not require signature.
Some carriers are following special Covid-19 protocols and will not require signature, or will give you the option of opting out of requiring a signature.
Due to the unpredictable signature enforcement, we highly recommend shipping the product to an address where someone will be available to sign, or immediately retrieve the parcel.
Due to the global pandemic and increased demand, shipping has become very expensive. Conductive Labs reserves the right to charge for re-shipping a product when an item has been returned due to a carrier being unable to deliver it. Please keep a close eye on tracking.
When shopping on the Conductive Labs website shop, you will see a list of choices for shipping once you put an item in the cart.
The carrier choices vary with the destination, size of package and cost. We use Easyship.com as our postage provider and they will typically offer the best price for the money, the fastest and the cheapest options.
We recommend choosing an express carrier such as DHL Express, UPS or FedEx. It costs more, but they will typically facilitate getting through the customs process faster than regular mail (such as HK Post) and with more tracking detail.
Unless you are in the United States you will most likely have to pay import tax, duty and or VAT imposed by your government.
When ordering from conductivelabs.com, in addition to shipping cost, you can see the estimated tax when adding items to the cart.
Check with your Country’s Customs department website for rules and fees. If your parcel ships by express carrier, you may also be charged an additional fee (around $10 USD) for their handling of the customs processing. We ship from our warehouse partner in Hong Kong.
It depends on the delivery method. We recommend choosing express delivery when possible. The actual time it takes for the carrier to get your parcel to customs, and how long customs takes to process it is of course not within our control. Express delivery services such as DHL, UPS and FedEx typically handle customs processing faster than regular mail, such as HK Post. When you place an item in the cart on our shop, you will see an estimated delivery time for the carriers offered.