A summary of the enhancements made since the 1.1.075 release (see beta releases below for more details)
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.
MRCC USB Device enumeration and naming enhancements. Allows for better operating system differentiation when more than one MRCC is attached. Prepares MRCC for Microsoft Windows MIDI Service when it is released.
Modification to LED control library to increase color fidelity at low brightness.
Warning: this release changes the format of the MRCC’s USB Device name (if you were not already using beta version 1.1.089) so it will undoubtedly mess up the naming in your DAW or MacOS Audio MIDI settings. See instructions on the Firmware Updates page to clear old names from the OS so the new name(s) will be used.
Feature Enhancement
Another tweak to USB Device naming: 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.
Once you change the name, you may need to follow the procedure below (see the previous beta release notes) to remove Windows cached USB devices.
Warning: this release changes the format of the MRCC's USB Device name so it will undoubtably mess up the naming in your DAW or MacOS Audio MIDI settings. See instructions below to clear old names from the OS so the new name(s) will be used.
Fixes: Enhancements to 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. However, we have tested numerous transfers of >150K files, comparing the received input with 100% success. It was tested with merged clock and other MIDI data. 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:
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" settings on Settings page 4/4. See instructions for clearing Windows USB device cache below.
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 (please let us know if you see an app that uses 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 MRCC’s 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. We are looking into making unique USB Product IDs for MRCC names in a future FW update.
We have discussed these changes with the Microsoft MIDI evangelist and believe MRCC is now ready for Windows MIDI Service when it is ready.
For your OS to properly enumerate the new MRCC device name and serial number, it is necessary to follow the steps below.
Instructions for clearing the Windows USB device cache of old MRCC entries
Since the MRCC name will be cached in Windows USB cache, it is necessary to follow a procedure to get the device name(s) to update:
1. If desired, change the MRCC device name to the name of your choice, e.g., MRCC-X (it’s on MRCC Settings page 4/4), update the MRCC firmware (if you haven't already), then turn off MRCC.
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 are gone. Go to step 4.
For Windows Device Manager, open Device Manager and 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. Shutdown (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 OSX:
1.After updating the MRCC... Open Audio Midi Setup on mac, 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 PC (usb) port, 5. 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 the macOS Audio MIDI Setup will cause unpredictable behavior and will require you repeat steps 1-5 above to create a new instance.
Features:
- Number of simultaneous routes (per patch) allowed/saved/recalled has been increased 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.
Bug Fix:
- MRCC MIDI Cntrl Port won't save when greater than P06 (P07 through P12 would revert to "-" on power cycle).
Note regarding this change: we have not tested any performance impacts of having so many simultaneous routes. If there is MIDI clock and data going over a lot of routes (>50), at some point it could introduce latency and jitter, or dropped MIDI messages.
Preferably, only route what is needed using the buttons on the MRCC and save patches for your most common configurations. We made it easy, with buttons!
Routing everything to everything means that every input is being merged to every output. At some point this will over-saturate 5 pin DIN outputs with more MIDI data than can be sent at 31,250bps (the MIDI spec speed of a MIDI port).
Too much MIDI data may over-saturate vintage synths that can't keep up with a maximum MIDI data load. Every MIDI device will have to process every MIDI message for channel number to see if the data is meant for it, or something else. Same goes for MIDI devices with processed MIDI thru ports, they may have trouble keeping up. Just like when Ethernet networks went from using Hubs to Switches, this is one reason we use MIDI routers, so we don't flood every device with MIDI data unnecessarily, risking adverse effects.
There are many variables, YMMV as MRCC has a very fast processor so it can handle a lot of data, but that can't be said for everything in your MIDI "network".
Please report any adverse results of having or saving more than 50 routes in the MRCC beta forum.
BUG FIX:
bug: Transpose of +12 will not load after saving - fixed
bug: Transposing Notes - min Note value allowed was 1 now it is 0 - fixed
bug: Split/Layer - Layer min note value allowed was 1 now is 0 - fixed
MRCC_v1.1.071 Official Release
Thank you to our forum members that helped with testing beta releases!
Fixed in this version
Corrupt text on the Routing Matrix screen in some circumstances, such as when using the navigation buttons to "zoom in" on virtual port routings, then pressing an input or output button.
Release notes from the most recent Beta releases (older release notes available at the link):
MRCC_v1.1.068
Features:
Added current Preset Name on Load/Save screen
Added screen idle timeout to prevent OLED burn-in when the MRCC is left on a lot. The "Screen Off" time can be set on Settings page 2. The screen will sleep when MRCC is "idle" (no MIDI notes). However, the idle timeout reset ignores Clock, ActiveSensing or TimeCodeQuarterFrame MIDI messages and will timeout despite those messages being present. Tap the green button or any other button to turn the screen back on.
In Channel Map modifier: added a new Chan Source = "-" (none) in lines 2-4. This enables a bunch of Channel mapping possibilities. For example, if the desire is to only map a single channel, set Exclusive to Y, set Channel map line 1 to the channel to map from, and Out to the channel to map to. Set channel map lines 2, 3 and 4 to none (-).
Removed the SHIFT+ required in SAVE / LOAD 'ing presets (no safety on the preset overwrite!!!).
BUG FIXES:
Major overhaul of System Exclusive (SysEx) message handling. MRCC should be able to handle any length data to all possible out ports including MRCC to MRCC & MRCC to Remote 7. Please note: It is possible to overrun the MRCC's internal buffers when sending large SysEx files from very fast USB to very slow 5 pin DIN outputs. The sending software should throttle the speed it sends SysEx. Also note, if sending large SysEx files, be sure to temporarily turn off any other MIDI data sources. Once the internal buffers are full, MRCC will block MIDI data on merged inputs, but better chance of success if its not having to handle clock and other messages while the large transfer is happening.
The last selectable preset name was 128 (F25) - should have been 127 (F24)
Fix some Preset save issues. If you experienced an issue where after saving a patch, it changed back to Red from Green, this should fix it.
Activity Screen always shows the correct Preset Label
When routing remotely and holding the "Y" 5-Pin #1 is not showing MIDI activity
Fixed some User Label Save/Delete/Assign issues.
MRCC_v1.1.052_04-04-2022
BUG FIX:
Program Change messages fail to route when on same port as MRCC MIDI Cntrl, despite being on a different channel.
Just got my MRCC and after a bit of smashing my head against a wall virtual cables make sense, all good! This is going to save me a lot of pain in the long run for sure. One thing I can't figure out and can't find references to anywhere is MPE compatibility or lack thereof. Here's my use case: I have my Linnstrument 128 connected to the MRCC via USB. Works. I route that to my Mac on Port 1. Cool. Ableton sees this and controls an MPE-enabled soft synth just fine, but only as a single channel MIDI device, not as an MPE controller. I can't seem to find any setting - either in Ableton or the MRCC - to tell either device that the Linnstrument is sending MPE data. By contrast, when I connect the Linnstrument via USB directly to my Mac, it knows that it's getting MPE data without me changing anything, and it works correctly, so this tells me that the Linnstrument is at least sending the right stuff.
So! Is MPE possible via MRCC? If so, what do I need to do to make it clear that that's what I want to send? Thanks!
Duhhhhhh I found it. But I'll leave this here to help others. In Ableton MIDI settings pick the Port your MRCC is transmitting desired data on and select "MPE". That was... easy. Eventually.
Hello
Been a while since visiting this forum. Have been enjoying Elektron’s recent Firmware updates …
And on that note; Simple question - Has the MRCC firmware addressed the issue of ‘Program Change’ that will endeavour a greater potential in conjunction with the Elektron ‘Song Mode’ … ???
Btw. I’m still on the default MRCC firmware when I received the unit a few months ago now.
On my MRCC it's often hard to tell if a PC OUT Port LED is lit (blue) or dim (pink). The difference is really subtle – even if I look at it from different angles. I tried all LED brightness levels, but that doesn't solve it. I assume it's mainly a hardware issue, because it's worse with some of the LEDs.
I guess a solution would be to switch the dimmed LEDs just completely off in a firmware update. Would that have any downsides?
I recently noticed that the display on my MRCC is very hard to read, I've had it buried in the rack, and did not make any changes for ages, so I'm not sure if this is something new, or was like that for a longer time. Have anyone seen a similar issue?
Pictures, unfortunately, does not represent the issue accurately, it does look worse than on the pics
Thank you for MRCC Video Course! It may be missed, but I recommend to watch it - it makes everything more clear.
I have question regarding (my new) knowledge about tempo and arturia devices (just watched #17). I use KSP as main clock source - it’s easiest and fastest way to change tempo. And it’s right, when I stop KPS sequencer, it stops sending tempo signals. I also use MRCC to send tempo and start/stop for few other machines.
Internal MRCC clock may send it all the time, but it’s based on internal clock only (correct me if i’m wrong). It is possible to use external clock source (KSP), but when it’s stopped, MRCC will keep sending tempo?
Hey everyone! I recently purchased an mrcc 880 direct from the website. I got an order confirmation from the site but never got one to my email. Is this normal? Has anyone else experienced this when they purchased this device? The company is still in operation right?
I was browsing the forum for some time and checked the manual, but I can't seem to find an answer to my question/idea for the live setup.
What I am thinking about is, using a small midi controller, plugged into INPUT 01 of MRCC
The main MIDI keyboard - IN 02 of MRCC
A number of rack synth modules plugged into OUT 1-8 DIN out
And being able to change which synth/port the main keyboard is sending the messages to, using the small MIDI controller from INPUT 01
The 3 solutions that came to my mind are:
- Changing MRCC presets from the midi controller, and having a different routing on each one of them - this doesn't sound ideal
- Hooking up "BLOKAS MIDIHUB" between the main midi keyboard and MRCC - and change the output midi channel based on the midi note from some small midi controller plugged to the MIDIHUB as well
I would like to avoid involving a PC for this, also part 2 of the plan is to control SampleTank Reverb and Delay over midi from the same small midi controller, on the other side of the studio, a bit further from the FX themselves and MRCC itself...
Is there any easier way of achieving this by any chance? Seems like a simple thing, but somehow I can't come up with a better solution.
![[Image: L1cWHDI54fgrAn_tedNOziH7HiRiQ9rlIhiN0Ezr...authuser=0]](https://lh3.googleusercontent.com/L1cWHDI54fgrAn_tedNOziH7HiRiQ9rlIhiN0Ezr3kYkkNQvGYwvdrljbBTSYgkE4fL_QAqKnoy61muB7xHR8GSFCTKHqrqWf50OqkcSpsaS9oBY5E8MkiVw8Nf9uy56Wl0Xf_Ii6H0UBG5DRbcg06aCaWJIkC9IISQU9t9rWsdqFz5Fzm0w3R4LZIwb_az-mFnokwlbhLbc2J_vCyUyEVx9Cqt2o27szV4aFZOy_On51fJN4iut3hKs8XjAvXpHZnZ3kpXNcWFyDvBHStEqcaHc8jEMUupEtaS4JKotLURAGjqd1CdVVe7TgluKaR1tIzMveQWq5N0llZ0QqobR-lWTA-uPRqq5_rF7RQax7AmZJsWTlYLxRYvVE_3N2EfahSlqKCdEYVkiXll1dt0e_a1vycN2X0F_ceRDNJ1eWbeAA1ov5M-uvrtIANctmJJILg31xj1aDac1OcNnASUMEjXVXG3STFLOnRNKbGyQ2ZOTs5s9olw7Lkln_EQJyyxnBdnGt7mIA7YbCk8Biqjxuu1jFKWDkfuKDKt34I0qv4mPjWNSgTGQX_ojIGZT-Bg0jnJsTooGpF-g4_CpjyffRkYDfN6dMDCKk5acM5hBz9sK-Rw1Qee16Kf1-F-gwJYOQldvGm2Si5RiiUmsz6CrnH3m-JBePo6lC9ZDvxiF8ZxbSrTmFj7yuM9bhStpnccdr8whnxjpiAVbo55Z_zwmCizDlvctX8IvSWB81sIt7dzxJTdyzSuusPCXDYu5oFmqsVuP6yweOj33M4i9iIZGGJ-RbfwMpuX97dqFMaFMWw7vyrxkLU2NokVerwuM-OQcW7oR-SS8J8QYMhQH3jmdeaKPYI_z9XCtfMWoLiK-CdBTn5HbcelESyQqOom3I4rKJFig-eDkjzkXyEzlI9_7MbrOfiNN7irsw__sXg09TqN1Qe_bJ35YIGiuj_japsPdAsKepLzd6octrHy11Xc=w577-h1287-s-no?authuser=0)
Shipping/support