I'm sending prog changes from DIN1 on channel 16 and selecting MRCC presets. The preset number on the activity screens corrupts.

Hi,
I want to convert MIDI CC parameters from Faderfox MX12 (MIDI din input) to Allen heath QU SB (MIDI USB) effects parameters (NRPN hex). MRCC could do the job ?
Thanks
Guillaume

This isn't to do with the NDLR directly but rather this web page. I generally check every morning for new messages and do a quick scan of each NDLR area. This is on my iPad while slurping coffee. The other day I noticed that the "NDLR Librarian API" was missing however ... later I checked on my desktop and it's there. Back to the iPad ... not there!

Has there been some change to the web page recently that would do this?

Keith

This morning I am trying to send a sysex message from a controller connected via DIN and MRCC-A to a device connected on USB-A on MRCC-B

When I monitor the traffic, I see it going from the controller to MRCC-A, but it never seems to appear over on MRCC-B.
In parallel, I have something generating MIDI notes going from MRCC-A to MRCC-B and the receiving device plays just fine. 

Is there anything in the code/configuration that would prevent sysex going across MRCC connections?
If I press the "Y" button, I see the in/out LEDs are properly lit.

It could be some user config error here for sure, but wanted to know if you guys checked sysex between MRCCs.

Thanks

Sharing a new jam I've recorded yesterday.
It was inspired by sci-fi soundtracks and the NDLR once again proved to be a great centrepiece to control everything simultaneously~

https://youtu.be/6jutZr5Vg2w?t=114

I have tried for a week or two to learn how to route midi signals to their instrument destinations and to my DAW for separate midi track data. I have read the manual many times and once I finally set it up it all seemed quite simple. I will say it isn't exactly intuitive but once you get the idea of virtual ports then it really hits home.

My setup includes the NDLR, a bunch of hardware synths and Cubase on an iMac. My intent was to route the four parts from the NDLR to the instruments and to separate track in Cubase for real time recording and later playback (if needed). I like this strategy for a number of reasons - mostly though in case of a later reworking of the music idea with different voices or in case of recording errors with levels etc..

It worked great when I finally got a model of the virtual port idea in my head. Using the NDLR usb cable directly to the usb A and each "part" from the NDLR set up for usb 1 - 4 in matching with midi channels 1 - 4. So the Drone is output from the NDLR in midi channel 1 and correspondingly usb #1. The Motif-1 is midi channel 2 and usb #2, etc.. Then picking up the synth output channel for each usb port as well as PC port #9 - 12. Then setting each midi recording track in Cubase for the midi channel number and port from the MRCC was the next task. Once these and the audio channels for the synths were set up in Cubase I just hit record and played everything. Once finished I set up Cubase midi channels for return to the MRCC in the same virtual ports with each corresponding synth picked on the MRCC as well.

What kept giving me trouble was the idea of how to use the ports and midi channels as discrete routs to and from the NDLR and PC. I was picking up all midi channels on each of the four midi tracks in Cubase until I paired each port to the corresponding midi channel and it snapped into place. Sort of an epiphany once it happened. I doubt I'll forget the idea of the virtual port after that.

Anyway, regardless of preaching to the choir I am proud of myself for sticking with it long enough to make it happen. Here is a short 3 minute piece demonstrating the session.

Sorry if this has been asked before but the only mention I could find was for the MRCC and I replied to that post.

I believe there is a need for a NDLR editor.

The screen is too small and too hard to read. Sorry I was born in 1954 and my eyes were never that good to start with. You should see how many Magnifier Setup Solutions I have tried just to be able to use the NDLR.

The menu diving and switch/knob combinations/back-and-forth required to do things is a perfect example of why most people HATE engineers. And I was one for decades so I took a lot of guff from those poor souls I was tasked with supporting.

Please don't ban me. I LOVE the NDLR. But even Roland released an editor (!) for the TR-6S and it made a huge difference in usability of that drum machine. And the NDLR is far more complex.

If you need to do a Kickstarter for an editor I will contribute. Or do a Mark II of the NDLR with a decently large display and enough memory, etc. I will contribute to that also.

Thanks!

Hi! Having RTP-support would be a killer feature for me, since I could integrate the MRCC with other products - I have lots of midi devices...
Do you plan to have RTP-support anytime in the future?
Thanks a lot for your great device!
Stefan

Could the Scale Degree buttons ( centre circle) be made to be triggerable from an external MIDI device in a way that is AWARE of scale 

for example , if NDLR is set to play  in C major, then the C key on my external keyboard would trigger the I ( 1st degree )  , where as if NDLR is in E major, then it would be E that triggers the 1st degree.. etc

thanks

Phill

Using the NDLR and MRCC with a large format modular and Eurorack modular, a Prophet 08, Dreadbox Erebus, Moog Matriarch, Oberheim OB6 and a Roland System 8. Recorded in real time to Cubase and video edited in Final Cut Pro.
Having a lot if fun getting to know the Creatve Labs gear!

https://youtu.be/8I5leAFhOIw