You can get to the MIDI Mixer by pressing SHIFT + the lowest Knob on the left side. It generates CC7 on the channels you have assigned your parts to.
Works well......BUT: If you use the polychain feature for the Pad it goes only to the Pad channel itself and not to the chained ones.

So this is another bug for the list of bugs that did not get shorter fot a very long time meanwhile....

The answer will be: There is no space left in the code to fix that.....as usual... 

Thank god I have a Blokas MIDIHUB so I can make a workaround and the NDLR can stay in my setup.

I'm using a brand new MRCC 880 out of the box, plugged into USB power (no computer).  After some tinkering around, I discovered that nothing plugged into Din1in seems to work, but the trs port does (with the right adapter). Before I return to my retailer, is there anything I should try to get the DIN port working?

Hi-

I am fairly new to more complex midi setups, so it's quite possible I am doing something wrong here. 

Setup is:

• Novation Summit (local off and transmitting on CH 1) MIDI OUT -> 880 1 IN
  
• Polyend Tracker MIDI OUT -> 880 2 IN
  
• 880 1 OUT -> Summit MIDI IN (receive on CH 1)
  
• 880 2 OUT -> Hydrasynth Explorer MIDI IN (local off, receive on CH 2)
  
• 880 3 OUT -> Korg Poly 800 MIDI IN (receive on CH 3) *I am not sure how well this old synth will work with my desired setup
  
• 880 4 OUT -> Polyend Tracker +
  

1. The Summit will be used as a MIDI controller to play notes on any of the above output devices
   
2. The Tracker will sequence the synths connected to the 880 Outputs
   
3. I have SUMMIT IN 1 and 2 linked to all four outputs
   
4. It works with only the Summit (local is off, so it has to be getting the MIDI notes from the 880) 
   
5. None of the other devices seem to receive the MIDI data
   
6. I have tried it with and without Chan Split
   
7. I have tried changing the output devices receive channels to ALL/OMNI and specific channels
   

My apologies if this has already been covered - I couldn't find anything relevant - or if this isn't the correct forum; however...

The biggest issue I've got - and have always had - with my studio setup is distributing some form of time-based sync function across all my synths, keyboards, modular and effects, so that the arps, sequencers and pattern generators, et al, are all in time, always!

So, I am renewing my investigation into the best way to go about distributing MIDI Clock - or whatever timing protocol(s) I need to deploy - throughout my entire setup, hence this post!

The Details
I seldom - if ever - move my studio gear around (save for when I play a very simplified setup 'live'); however, I want to be able to be able to sit down at ANY device (MIDI controller keyboard, sequencer, pattern generator, arpeggiator or synth) and have everything else synchronised to them when I press 'play' (or start arpeggiating on a synth!).

That means either my Conductive Labs NDLR, Arturia's BeatStep Pro, Arturia's KeyStep 37, my Vermona Melodicer, Pamela's New Workout, my Doepfer Darktime, Korg SQ-1, Behringer 182 (via a Doepfer A190-4), or my (Cubase) DAW - when I'm using it - puts out appropriate clock/timing info (usually MIDI 24PPQN MIDI Clock) which is distributed appropriately whenever any one of these devices are actually running.

[Note: Unfortunately, the NDLR appears to put out MIDI Clock even when it's not actually playing and requires menu diving in order to turn it off and back on - something I'm loathe to do as I lose any creative spontaneity - whereas the Melodicer module is never, ever off, which is why I slave it to incoming CV timing info via Pamela's!]

I currently have everything (including Pamela's and my Arturia DrumBrute!!!) synchronised to my NDLR via an ageing (and faulty!) parallel port MotU MIDI Express XT, successfully operating in MIDI "Merge All" mode for ALL of its 8x8 MIDI ports ... but I have got to come up with a better solution in order to avoid inevitable MIDI loops and to reduce the sheer amount of MIDI sync timing data flowing around every, single device in my setup!

I'm seriously considering investing in a Conductive Labs MRCC - to replace my old MotU XT - simply so that I can create an appropriate distribution matrix which can be recalled at the flick of a switch.

There are currently no MIDI loops as every device is configured and connected either as a MIDI input devices or MIDI output device (essentially in a star fashion from the MotU Express XT) - with either a MIDI In or Out jack connected to it - with absolutely no device acting as both. No device acts as a MIDI thru - myriad Kenton boxes perform this function. A few CV-based devices are (re-)patched appropriately to send or receive their timing info.

There are no innate issues causing fundamental problems with this setup, apart from the following usability restriction and the sheer volume of MIDI data being distributed:-

1) The fact none of my synths (or MIDI controllers) currently receive any MIDI in data, so they cannot be sync'd to a single master clock without causing MIDI loops;
2) The amount of MIDI Clock timing info being sent to (and received by) all connected devices.

So, any ideas, folks?  Can the MRCC do all that I need? What are the issues / limitations, if any? 
Thoughts and constructive comments welcomed, encouraged and much appreciated.

[Additional Notes:-
MIDI gets into my Eurorack setup / modular environment via a Doepfer A192-2 and out of it via the aforementioned A190-4.
MIDI gets into and out of my DAW via a USB3-connected ESI Audio M8U eX, alongside the aforementioned MotU XT coupled to myriad Kenton Thru and Merge boxes which feed the M8U via a single port.
I try to only ever use MIDI over USB for firmware updates, initial setup/config matters, and sending SysEx patch info to individual devices, disconnecting them at source in order to avoid the inevitable ground loop and graphics whine issues, plus the ensuing confusion at the DAW end.]

By-the-way, apologies that this is so long but I realised most parts required a little bit more 'clarification' after I'd initially finished writing, solely in order to communicate exactly what I've got and what I'm trying to achieve. Sorry 'bout that!  Hopefully not a TL;DR post...!?

Cheers,

Steve.

PS Am I correct in my observation that the NDLR continues to generate MIDI Clock info even when it is not 'playing'? Disabling its Internal Clock setting (or simply pulling out the appropriate MIDI jack at the NDLR end!) removes this data stream, so it's definitely originating at the NDLR even when it's not running. Is this operation correct / normal and, if so, why and, if not, can it be configured differently?

PPS  This apparent clocking issue is why I sync my entire setup from my NDLR.

Hello,

I just received a new NDLR and upon starting to learn it found a strange issue
It is related to the change of the pad notes - the range parameter, and then
moving to different chords.

I have the NDLR connected to the computer and using a sequencer and a software synth
and I am recording the midi input that comes from the NDLR into the sequencer.

The p-chains parameter is set to 1, so all the notes should be sent to only 1 midi channel.

The issue is occurring when increasing notes for the pad (the range parameter) and then changing chords.

I started with 3 notes, then increase to 4, change chords, works fine, 
then increase to 5, right away I see an additional note, so has 5
but then when I change chord it play a 3 note chord
then I decrease the notes back to 4 and now it is playing 4 notes
then I repeat the whole thing and the same issue.

Firmware is 2.0.011 (I did not update to the newer one)

I discovered that this happens when the spread is 2 or above
when it is 1 and I increase notes, it always work (I went upto 7 notes)

I am attaching a screenshot of the midi recording with an explanation
of each step I did, and would like to ask about this strange issue.

Thank you

Attached Files

Thumbnail(s)
   

The MRCC has been amazing!
Thanks guys.

Maybe I'm not getting something, or maybe it can't be done, so I'm hoping to get clarification either way.

I have all my hardware synths connected over standard Midi cables (so far so good)

I want to connect the Torso over USB so it can be powered and take care of notes and sequencing, this works great too.
The issue I'm having is that I also want Bitwig to follow the Midi clock of the Torso through the MRCC.

This is where I can't join the dots.

For the sake of argument let's assume I have all of my setting correct in the Torso and Bitwig, 
I just need to know the steps to on the MRCC to make everything talk.

If there's an obvious button combo that I've missed I'd love to hear some input.
Many thanks in advance 

I am using CC1 remap to take cc32 and remap to 0 so a device can accept program changes and bank changes. Then I take CC0 and remap to cc32 or anything else to stop the device from receiving that other cc0 message.   Unfortunately it maps cc32 to 0 and then at the same time takes its remapped 0 and remaps again to whatever I chose 0 to remap to. So it can not remap independently, nor can I filter cc0 separately before the remap.

find my MRCC has horrible LED bleed / spillover, so much so that is difficult to distinguish whether there is a routing on a given output or whether it's a spillover from a nearby output.

I might consider taking the unit apart and putting some separators between the LEDs or wrapping them in electric tape or something along those lines. 

Has anyone done something similar? 
Is the internal design preventing similar solution somehow?

Just scratch that 

This might be a stupid idea, anyways as I am struggling a bit with where to place the MRCC, I would at least theoretically welcome the ability to rotate the display 90 degrees to be able to read and control it comfortably in case the unit is placed / mounted vertically.

Obviously if the screen is not regular square with same horizontal and vertical resolution then it's a no-go, but if x=y, then maybe the display could be rotated via firmware?

Sometimes something doesn't work and it makes no sense unless the cable must be broken. 

New extras function would allow to specify input and output DIN ports and then send data from the output and evaluate if it is received at the input correctly, or if the data didn't make it through the cable.