After extensive testing with multiple cables and devices, it has been discovered that the port 6 TRS A/B on my MRCC is bad. There is no signal being received, no indication in the display, nothing. I have reported this via the support form but wanted to bring it here hoping that I may be doing something wrong.

I thought I was going crazy trying to get things working, but it turns out that signals are not being received. I am curious(I did read the manual) about how one would go about routing when there are 2 ports for the TRS jacks. There isn't anything in the manual for running both ports at the same time.

Have others experienced this?

Joshua
_____________
Digital Analog Daily

Years ago I sold off more than half my gear and said never more. I was good, until I bought a NDLR and then the proverbial floodgates opened and I was on the buy more gear merry-go-round. That is just an intro to justify my buying myself a Behringer Solina for Christmas, had it delivered on the 24th. I've wanted a Solina since they announced it an eternity ago. After three years of waiting, I figured it must be a hoax. Eventually, they did trickle into the market, and now they are super easy to get.

I wanted a Solina specifically to do Pad detail with the NDLR. And, sure enough, it does excel at what it is intended for. Satisfying throwback Solina sound. The range of notes it responds to is rather limited and the NDLR easily generates notes beyond its capability. Because it is just a one trick pony, albeit with modest variations, I won't be using it all the time. Probably not all by itself much either. It will probably layer nicely with other pad synth sounds that will sound when Solina gives up.

Anyway, just thought I'd mention it here since it works so well with NDLR Pads.

Hey! A little confused and wanted to see if someone could post their MRCC and Keystep Pro configuration when the Keystep Pro is connect into the MRCC via USB. Can't figure out how to assign a different hardware synth to each Keystep track via MRCC. I know how to route without the MRCC, using regular din midi ... but just lost with this setup. Appreciate it!

Over the last few months of owning the MRCC, I've found that it frequently requires restarting both the hardware connected and the unit. This tends to be required more for hardware connected via USB but happens with DIN connections as well.

Hardware list:
Hydrasynth - 5-pin - In/Out
Elektron Digitakt 2 - 5-pin - In only
Elektron Syntakt - 5-pin - In Only
Elektron Octatrack - 5-pin - In/Out
Waldorf Iridium Desktop - trs(mrcc)/5-pin(Iridium) - In/Out
Arturia Keystep Pro - USB - In/Out
Windows 11 - USB PC Main - In/Out

I've had to turn off the MRCC several times because the signal is not stopping. This could be due to a lack of experience and understanding, which is why I'm coming here to see if others have similar issues. If so, is restarting things just the normal path to enlightenment?


Joshua

Hello

I am currently using the MRCC (MIDI Router Control Center) with my Mac to route multiple MIDI channels between various devices & software but I am running into a problem where certain channels aren’t being routed correctly.

Specifically; MIDI signals are sometimes being dropped or mixed between devices; leading to unexpected behavior in my DAW and external MIDI hardware. I have checked https://conductivelabs.com/forum/forumdi...hp?fid=23/splunk reference guide but still need advice . 

I have checked my connections and made sure all devices are recognized; but the issue persists. Has anyone experienced similar issues with routing multiple MIDI channels, especially on Mac?

Any advice would be greatly appreciated!


Thank you !

v1.1.086

Using the 'Show Midi' utility, I can see there are no 'Note Off' being generated when playing Drones and Pads.

Note Off is only transmitted when turning Drone and Pad Off.

Motif 1 & 2 perform as expected.

Am I missing a setting?

Surely this is not expected behavior..

Thanks

When I look at a score, I see geometric figures, not noise. Often, what I see resembles Koch snowflake fractals. For instance, a square wave input might produce two notes. If you delve deeper, you would find a sub-square at the high level and another at the low level, resulting in four notes. This recursive digging can continue indefinitely.

By adjusting the pulse width, you can influence the tempo, while altering the signal height affects the spread of notes. This adjustment also determines how deeply you can recurse. Eventually, you can transform the square into other shapes.

I hope this explanation makes sense.

Hi, 

Trying to connect my Android tablet to the MRCC. I'm looking to use my Android tablet as a TouchOSC device to control synths on other MIDI ports. 

Is this possible? 

1. Android tablet plugged directly into USB Host A, B, C, or D

2. Tablet can receive power from USB Host A-D (i understand that this might be really, really weak power)

3. Software on Android tablet will see MRCC as MIDI device, can receive MIDI from MRCC, can send MIDI back to MRCC.


Note: I'm not committed to the idea of the Android tablet connected to USB Host A, B, C, or D; it just seems like the easiest.

If I have to use something like...

Android tablet <-> USB MIDI Interface <-> MIDI DIN IN and OUT

...I'm OK with that, too. I would just need to know how to power the Android tablet while the USB port on it is occupied by the MIDI Interface.
  
Thanks,

Nick

Hello. The tempo on my ndlr has begun showing 480 BPM yet is hooked up to my DAW set at 120 BPM. I've just noticed if I slow DAW down to 20 ndlr shows 80 so 4x20. 480 = 4x 120. It's not playing at 480 BPM. Any thoughts as to what might be occurring? It's set to clock in USB1 and 'tic' in red is flashing rapidly. Don't know what tic means. 

Thanks

Rob

hi does anyone know if there's a way to send midi cc to the MRCC for start/stop messages.
there is midi cc 30 for clock enable, but not cc for start stop of the clock... am I missing something, or is there a chance this could be in a future update?

I just wanna keep the clock enable on and then start and stop the clock via a midi controller

mikael