Hello, new noodler here. Query about the 1/8 clk setup:

If I clk out to a Rucci Clock Manipulator and then return its output to clk in, what’s gonna happen?

https://handmadeelectronicinstruments.co...nipulator/

Manual says:

“Clock In” must be enabled in the Settings 3 menu. It must be set for “ClkIn CV”. Once this is set The NDLR uses the input pulse signal as it’s internal “heart beat”.

But the Rucci gear uses the clk out as it’s source material, so I’m guessing it wouldn’t works as intended?

Thoughts, criticisms, jokes all very welcome!

qdrnmx

Hello,

first of all thanks for finally building a midi merger, that is also compatible with linux. Even if only by not needing a PC at all. And, well, stick to class compliant usb.

This is more a general inquiry, more of a buying decision helper, as I do not have this device yet. But as they are supposed to be back in stock shortly, it is time to get serious. If this is the wrong subforum to ask this, lets call it pre sales inquiry, please feel free to move it around.

My proposed setup is rather simple:

I have all 5 DIN inputs connected, one USB host and one device on TRS-A. Makes up for 7 input devices, whereas 9 instruments are connected to DIN out 1-9.

As to be guessed from the topic, I would like to do channel based routing/merging. That is, everything, on any of the 7 inputs, that is being send in on midi channel 1, is being merged an send to DIN  out 1, everything on any connected input on midi channel 2 is being merged and send out to DIN output 2, you get the idea, continue up to midi channel 8 to DIN out 8.
Finally,  everything on any input on midi channels 10-12 is being routed to DIN out 9. Just 1:1 routing and merging, no channel rewrite needed. 

I addition, midi clock is being received on the TRS input jack, and filtered on all other inputs, but only distributed to DIN out ports 1,3 and 5. So I would need filtering on the output ports as well.

Could that setup be accomplished with the MRCC? Not sure, wether there are enough layers for channel based routing, if possible at all? Maybe I just have not comprehended the videos well enough, in this case please bear with me.


I am not a native speaker, so if anything is unclear, please feel free to ask

Thanks

I really need more inputs any chance of adding more please

Just wanted to drop by and say that I LOVE the features and functionality of the MRCC. I ordered one last month along with the Remote 7. I do have to get off my chest that I was not at all thrilled about the shipping from Hong Kong (and if I knew that was going to be the case before I placed my order I may have gone in another direction...)

It really would have been icing on the cake to have had a couple of MIDI IN's on the Remote 7. After ripping apart a portion of our studio to wire the Remote 7 to the other side of our console (the supplied Ethernet cable was perfectly long as well!), and then a few weeks later installing some new analogue synth rackmount gear that unfortunately needs to dump patch data and the such over MIDI, it would have been great to have been able to go MIDI IN into the Remote 7. We ended up having to rip everything open again to run midi cables from the gear back over to the MRCC (so in hindsight pretty much defeating the need to have the remote).

I did just read that we can connect another MRCC unit to the other one via Ethernet (and I am seriously considering getting another one), however, it is a more expensive route which I am sure not everyone can afford. An expanded remote with at least 4 MIDI IN slots would be a solid way to go.

While playing with my routing, I noticed a curious thing: it seems that some USB MIDI hardware (in this case, Morningstar MC8) only seems to work on USB port A, but not on USB port C. I verified other hardware (Keystep) works just fine on all ports. I also noticed USB keyboards only seem to be supported on USB port A. Is this by design (not mentioned in the manual I think) or a bug?

I have two esi m4u-xl's that I use(d) to route all my synths in and and out of my pc. Now that I've got the MRCC I was wondering if I could use them in the usb host ports. They're midi class compliant but only input and output ports 1 out of the 4 work when I plug them into the MRCC. Any chance this might change in a future firmware update or is this a limitation of the hardware?

I have an Atari I like to sequence off, the MRCC only lights up as receiving midi data when I plug it into input 3, none of the other inputs seem to like it. Any ideas why? I mean it works but its a bit weird. I've tried a few different cables, they all seem to work fine when I plug my midi controller in directly to the other inputs. Sorta stumped...

Hi everyone,

I had a bit of trouble in getting the Polychaining function to work in Cubase. Since it isn't super straightforward, I will write below how to set it up correctly.

To tell Cubase what Midi Channel to listen to you need to filter out all other Midi Channels.
- This is done via the Input Transformer (on the far right at the top of the instrument Inspector see picture)
- Select Local
- Here you can either choose a "Channel Filtering" preset or create a new "Filter" (see picture)
- This has to be done with all the tracks you want to use the polychaining with.
- for the NDLR midi settings it's good to have the Pad on Channel 4, outputting Ch 4-5-6-7
- In Cubase you can leave "All MIDI Inputs" or choose the NDLR midi port. It doesn't matter unless you have other devices sending on channels 4-5-6-7.

It is a bit cumbersome but it's the only way I found to make it work.
I created track archives of certain instruments that I use the Polychaining function with. In this way when I load them in the project they are already set up correctly and it saves me some time.

I hope this helps

   
   

I wanted to try how MRCC would react to plugging in a USB hub, and I have to say I was surprised. I have two devices plugged to the hub, which in turn is plugged to USB A. MRCC is seeing those as being plugged to USB ports A and B. Nothing is physically plugged to port B.

Bug or feature?

Not a question, but turns out the included desktop legs are also perfect for wall mounting: