Many midi controllers have a lot of buttons that send CC only when they are pressed (e.g. drum pads), making them only suitable for "momentary" functions. If there was a modifier that, on the basis of sticky keys, maintained the on/off state and changed when pressed again, then they could be assigned functions such as mute track/record, etc.

In example Akai Midimix controller have problem with it - Mute buttons can be switched only between momentary and... doubled momentary (two values may be sent). It can't be correctly assigned to Toggle Mute function in BlueBox for example.

I seem to have encountered a bug where sometimes when scrolling through the ports on the routing page, the last 3-4 LEDs (for output ports 9-12) turn red. It doesn't happen all the time, and not with any kind of consistency, so I'm assuming it's a bug?

Hi,
It feels like there is a bug for changing the preset with program change.
I’ve set the midi input 2 and ch 16 as the MRCC control channel but when I send a PC-message on another channel but the same input the MRCC changes preset.
I have tried different input ports and the MRCC always changes preset regardless if the change messages comes on the specified channel or not. 
I have the latest available firmware.

Thanks a lot for a great piece of hardware!

While the chord sequencer is playing, opening the chord sequence editor causes all parts playing out of sync. Same happens when saving a chord sequence.

External Midi sync was used in this case, I have not tested with internal sync.

hello,

I would like to be able to toggle the individual parts via just key presses on the control channel. Eg C3 (pad), D3 (drone), E3 (motif1), F3 (motif2), G3 (all)

- The buttons on the unit are not as precise.
- Using the CC value is not practical for jamming unless you are using some dedicated hardware that you can program.

Thank you

Hey all,

... as a proud owner of a MRCC, which I received a couple of days ago, I tested some of my USB-Midi gear. Now my question.

Is there a kind of hand-shaking or switch-on procedure, which I should consider, when I plug in new gear in USB ports?

Background:
My Keystep worked instantly on the MRCC, but my Pyramid needed some attempts, before it was accepted. I cross-checked the Pyramid without changes with my MPC, connected it to one of the USB ports and it was plug'n play as expected.

I wouldn't call this an issue, but it makes me wonder:

• should I first power up the MRCC, then connect unpowered USB gear, and finally switch on the gear,
  
• or should I have MRCC with power off, connect all gear, and power on MRCC as the last,
  
• or doesn't such a procedure matter at all
  

I'm not sure if it's more hardware or computer, but iPad is computer anyway

I try connect older iPad mini to USB Host (usb-lighting) and also via USB hub to PC socket, but none of them see/hear midi connection. I just got MRCC and may not understand how to do that yet, but wondering if it can be connected like that? Or I should do that in other way?
Additional question - will devices connected via USB to MRCC be visible as USB devices from computer connected to PC port? Will MRCC work as USB hub?

Hello!

I had a chance to do some initial playing on the MRCC this week.  It is fantastic!  Super high quality all around.  The look, feel, funtionality, UI...  everything I have come to expect from you guys!

I love the options for screen and LED settings.  However, I have a small, but important bit of feedback from someone who has a medical condition that is highly affected by intense lighting.  The LEDs have brightness settings from 1-10 which is great!  However, even at 1, they are still way too bright.  I think the front, large lightpipes intesify there brightness as the smaller light pipes towards the rear (USB ports) are much less intense.  

I would suggest if possible to offer a lower setting where the brightest LEDS (selected ports) are the same brightness as in setting 1 as ports that are active in routing but not the selected ports (the dimmed ones - I hope that makes sense).  I would then make the non-select ports (dimmed ones) be 1/3 less bright or something so that they still show dimmer than the selected port.  Or maybe it is possible to add more levels - say another 10 and put make the current level 1 as the middle brightness and then the rest dimmer going down from there.

Right now, I have to cover them with masking tape for me to be able to use the device, which takes so much away from the beauty.   

I hope this is acheivable with firmware.

And seriously - I know I said this already - this instrument is just beautiful and way exceeded my expectations!

Michael...

Looking at the Blokas Midihub I am somewhat envious of the desktop editor and all the midi fx and tools they have. Obviously the MRCC has lots of advantages in terms of IO and the ability to program it without a desktop app, super quick routing etc. but man all those midi tools and chaining options look powerful. Midi delay for one would be really nice, but being able to chain randomization and note repeats / sample and hold etc. would be a great addition.

Obviously it's a huge tall order to ask for a desktop app to edit the config, but maybe something usable could be built into the existing UI.

Edit: Drool on this https://www.youtube.com/watch?v=ASruOUG2HIs

On the routing config page; tab to the input port, turn encoder lights cycle to the input port selected - that works. However, if I tab to the output port I cannot cycle through ports with the encoder.

On another note; the encoder has the same issue as the NDLR had; Sometimes a notch turn does nothing and you have to dial another notch in to get what you wanted. This isn't as big a deal as it was on the NDLR but it's still a little annoying and surprising to see the same issue on another product.