Computer Port Names are now "MRCC" only

[tielemat]

On Mac, You can deal with it , even if the procedure is a bit tedious : you can create and name midi devices for each MRCC virtual in and out port in Apple's Audio Midi Setup application. When linked to the corresponding MRCC Midi Device ports, applications such as Midi Patchbay and Midiflow (IOS but it works flawlessly on Desktop to) will recognise these Midi devices and the replace the twelve anonymous MRCC port with correct labels. It's a workaround :-)

[Jesse Johannesen]

Thanks Tielemat, I'll see if I can have Darryl mention this in the FAQ, that's good info.

---

Do you think you can send that image to me at support@conductivelabs.com? It's only showing up as a thumbnail for me here.

[bchampigny@comcast.net]

Latest FW (1.1.052) seems to change the way the MIDI ports in the computer are named.

Now ALL the ports are named "MRCC", where the previous version named them "MRCC Port #" (where # is port number)

Some software seem to be able to deal with that (doing their own suffix to distinguish them) (Bitwig & Ableton).
Some other software is now confused (unusable), as it expects a unique name per port.

Could we please have the old naming scheme back?

Best,
Joris

I have the same problem with Cubase 12 on OSX.  If I rename ports in Cubase from ‘MRCC’ to ‘MRCC In 1’ for example, it eventually reverts back to ‘MRCC’ and the track MIDI port assignments get messed up as they take all on The first MRCC port.

I have had to switch to using Reaper instead of Cubase for this reason since Reaper   At least appends a unique number to the MRCC generic label keeping the track routing in tact.

---

On Mac, You can deal with it , even if the procedure is a bit tedious : you can create and name midi devices for each MRCC virtual in and out port in Apple's Audio Midi Setup application. When linked to the corresponding MRCC Midi Device ports, applications such as Midi Patchbay and Midiflow (IOS but it works flawlessly on Desktop to) will recognise these Midi devices and the replace the twelve anonymous MRCC port with correct labels. It's a workaround :-)

I will try this method.  Currently the MRCC device is floating in AMS with no port connections and I usually get a greyed out duplicate of the MRCC when I have the vanishing pot name issue.  I can’t even use my preferred sequencer(Cubase) at the moment due to the port rearrangement.  Thanks

[bchampigny@comcast.net]

On Mac, You can deal with it , even if the procedure is a bit tedious : you can create and name midi devices for each MRCC virtual in and out port in Apple's Audio Midi Setup application. When linked to the corresponding MRCC Midi Device ports, applications such as Midi Patchbay and Midiflow (IOS but it works flawlessly on Desktop to) will recognise these Midi devices and the replace the twelve anonymous MRCC port with correct labels. It's a workaround :-)

I tried this method but I still get a new instance of the MRCC showing up with the original greyed out.  I might just have to switch to Reaper as mt main DAW u til this is fixed.