Downloads

1. Install the Teensy Loader program

Download the Teensy Loader for Windows: teensy.exe or for Mac: teensy.dmg. Save it somewhere convenient where you can find it, like the desktop.

More details for using the Teensy Loader (and the Linux version) can be found on the PJRC Teensy Loader page, but don’t download any firmware from there.

2. Download the latest MRCC firmware and unzip it

Download the MRCC firmware file from the list above and un-zip the .hex file from the .ZIP file to your desktop or another convenient location.

3. Load the firmware on MRCC

1. Connect the MRCC’s PC USB port (the USB type B connector) to your computer with the supplied USB cable.
2. Run the Teensy Loader program by double clicking it.

3. Click on File, then Open HEX File. Select the .hex file you extracted above. Alternatively, drag and drop the .hex file onto the Teensy Loader program.

4. Click the green Auto button so it is lit, then use a pen or paper clip to briefly press the recessed FW button (hole on the right-side end cap of MRCC).

It takes about 3 seconds to program. MRCC will restart once programming is complete.

Troubleshooting

• If you get a message that the file is too large, it typically indicates that the Teensy Loader program does not recognize the MRCC. First make sure you clicked on the green Auto button. You can ignore the error and try pressing the FW button on MRCC again.
• If MRCC is connected to a USB hub, connect it directly to a USB port on the computer while performing the firmware update.
• Try another USB cable. The shorter the better.
• If it still fails, the .hex file may be corrupt. Try downloading and extracting the .hex file from the ZIP file again.

Join our Discord server for announcements including new firmware updates, beta releases and release notes.

Warning: this release changes the format of the MRCC’s USB device name (if you were not already using the beta version), so it will undoubtedly mess up the naming in your DAW or macOS Audio MIDI settings. See the instructions below to clear old names from the OS so the new name(s) will be used.

Features

• Number of simultaneous routes (per patch) allowed/saved/recalled has been increased from 50 to 255.
• A number of routes counter was added to the top left corner of the Activity screen. The counter turns red once the maximum number of routes is reached.

Fixes

• MRCC MIDI Cntrl Port won’t save when greater than P06 (P07 through P12 would revert to “-” on power cycle).
• Enhancements to MIDI buffering and SysEx message handling. For large SysEx transfers (>10k), we suggest halting other MIDI sources to remove merged data, just to be on the safe side. MRCC can process messages after a SysEx end of message (F7), but will not interrupt or mix a SysEx message with MIDI realtime messages.

Enhancements to MRCC USB device enumeration

• Multiple MRCCs will now be recognized as unique devices by Windows’ current MIDI API when each is assigned a unique name (set on MRCC Settings page 4/4). It’s allowed to leave one MRCC named the default name, or change each MRCC to have a name with a letter, e.g., MRCC-A, MRCC-B, etc.
• MRCC “PC Name” (Settings page 4/4), which allows you to select an alternate USB device name for MRCC, has been reworked to prevent a race condition that caused the original name to re-appear sometimes.
• The name “MRCC” is also changed; trailing nulls were replaced by spaces. It might affect how the name appears in your software, unless you already changed the name using the “PC name” setting.
• USB MIDI virtual port names (Port 01, Port 02, etc.) are now seen as child devices of the MRCC device. Though these are not currently parsed by Windows’ MIDI API, some applications may use them. These port labels are used on macOS and will be used in the forthcoming Microsoft Windows MIDI Service.
• The USB iSerialNumber descriptor is now populated with the MRCC serial number. This helps Windows to see multiple MRCCs as unique devices. However, the Windows MIDI API may not see MIDI devices with a common USB Manufacturer and USB Device ID as unique devices. This is slated to be fixed in Microsoft Windows MIDI Service when it is released.

Clearing the Windows USB device cache of old MRCC entries

1. If desired, change the MRCC device name to the name of your choice, e.g., MRCC-X (on MRCC Settings page 4/4), update the MRCC firmware (if you haven’t already), then turn off MRCC.
2. Download and run USBDeview as Administrator (at your own risk), or use Windows Device Manager.
3. In USBDeview, look for a “Friendly Name” label of “MRCC” (or “MRCC-X” if you have renamed it), select it, then click on the column heading ProductID to sort. Select all 0490 ProductID entries, right click and select “Uninstall selected devices”. Check that all ProductID 0490 entries are gone.
   For Windows Device Manager: click View and select “Show hidden devices”, expand the “Sound, video and game controllers” section, find any instance of MRCC, right click it and select “Uninstall device”. Repeat for all MRCC devices in the list.
4. Shut down (or reboot) the PC, turn on MRCC, turn on the PC. The MRCC device name should enumerate with the new name.

MRCC device name instructions for macOS

1. After updating the MRCC, open Audio MIDI Setup and, with the MRCC disconnected, select and delete any previous instances of MRCC devices that are present.
2. With MRCC still disconnected, if desired, enter Settings page 4/4 and select the letter that you wish to identify this MRCC with (let’s say A).
3. Power cycle the MRCC.
4. Connect the MRCC to the Mac via the PC (USB) port; it should now show up as a new device, MRCC-A.
5. Disconnect and follow steps 2-4 for any other MRCCs, making sure to pick a different letter for each one.

Please note that changing the MRCC letter after it has been saved as a device in Windows or in macOS Audio MIDI Setup will cause unpredictable behavior and will require you to repeat the steps above to create a new instance.

1. Install the Teensy Loader program

Download the Teensy Loader for Windows: teensy.exe or for Mac: teensy.dmg. Save it somewhere convenient where you can find it, like the desktop.

More details for using the Teensy Loader (and the Linux version) can be found on the PJRC Teensy Loader page, but don’t download any firmware from there.

2. Download the latest NDLR firmware and unzip it

Download the firmware file from the list above, being careful to select the update for your version of The NDLR (original Rev1, or Rev2 with the red base). Un-zip the .hex file from the .ZIP file to your desktop or another convenient location.

3. Load the firmware on The NDLR

1. Connect The NDLR to your computer with a USB cable.
2. Run the Teensy Loader program by double clicking it.
3. Click on File, then Open HEX File. Select the .hex file you extracted above. Alternatively, drag and drop the .hex file onto the Teensy Loader program.

4. Click the green Auto button so it is lit.

5. Use a pen or paper clip to briefly press the recessed FW button on The NDLR. It’s between the pairs of MIDI ports on the back. It takes a second or two to program. The NDLR will restart once it is programmed.

Troubleshooting

• If you get a black screen after updating, double check that the correct firmware was downloaded. If The NDLR has a red base, download version 3.3.x. If it has a blue/grey base, download version 1.1.x.
• If you get a message that the file is too large, it typically indicates that the Teensy Loader program does not recognize The NDLR. First make sure you clicked on the green Auto button. You can ignore the error and try pressing the FW button on The NDLR again.
• If The NDLR is connected to a USB hub, connect it directly to a USB port on the computer while performing the firmware update.
• Try a different USB cable, or computer.
• If it still fails, the .hex file may be corrupt. Try downloading and extracting the .hex file from the ZIP file again.
• If you get a black screen after updating and you are sure you used the correct firmware, try resetting The NDLR to factory defaults using the boot menu: remove power from The NDLR, press and hold the Menu and Shift buttons, power The NDLR and release the buttons when the boot menu appears. Press the PAD button. If asked to confirm, press the Motif 2 button. Press the Panic button to exit.

Don’t worry, you can’t hurt anything by trying an update. Join our Discord server for announcements including new firmware updates and release notes.