aloha,

 today i tried to upgrade my ndlr, i went step by step until i did the paper clip thing, the moment i stuck the paper clip in the hole my ndlr went black. now i have no power, and cannot get it to power on.?

got any suggestions ? ... thank you.

I have my Morningstar MC8 plugged into the MRCC via USB. I am able to successfully route MIDI messages from the MC8 to my iPad/PC. However, I am yet to figure out how to use the Morningstar Editor setup this way. If I connect the MC8 to my iPad/PC directly it works just fine. Since Morningstar Editor uses MIDI to interface with the MC8 itself, I would imagine I could get this to work, but I must be missing something.

I just spent an hour trying to figure out why I wasn't able to map any routings from the PC outputs to DIN plugs.  I just happened to hit the max number of routings with no PC MIDI routings enabled, so I thought something was broken.  Rebooted, restarted the MRCC, swapped USB cables, etc.  I didn't even know that there WAS a max number of routings until I happened across another post on this forum (it doesn't appear to be listed in the manual either?)

A simple message popping up on the display screen that says "max number of port routings (50) reached!" would have saved me some troubleshooting time.

I have the NDLR and MRCC. I'm trying to sequence a synth (Polybrute) with the Octatrack and kept getting doubled notes. I finally figured out it was coming from NDLR. The OT is routed to all inputs (except its own) and so is the NDLR (plugged into USB). I read somewhere on the forums that the NDLR passes MIDI thru over USB? Is this what's happening? Strangely, I don't hear doubled notes on other synths so not sure what's going on. Please let me know what more I can provide to help troubleshoot!

So there is this entire category of threads on using the MRCC with a DAW, but I haven't been able to find anything that clearly explains how to use the MRCC with a DAW (in my case Logic 10.7 MacOS Monterey). I have read through a bunch of threads with people having the exact same issue as me.  I have found the MRCC quite capable in a DAWless setup, and am using my new Hapax quite favorably with the MRCC to control and sequence 10 different hardware synths. I cannot for the life of me figure out at all how to get Logic to do anything with the MRCC.  I gave up on trying to get Logic to see my Kronos Keyboard through the MRCC and have once again got it connected separately via USB and am using the DIN connection for the MRCC. Not cool, but okay. AudioMidi sees the MRCC and all the other synths.  When I route Logic back to the MRCC, the activity and routing window shows activity, but nothing is coming through the MRCC to trigger any of my hardware synths on any channels. I have checked the MRCC Filters page and have no filters applied. I have Logic Midi out set to MRCC Port 1.  I have tried it with the green button set to port 1, and other ports. The blue button set to port 1, and all other ports. Nothing works.  

I know other people have ended up doing a Zoom session with Jesse to figure this out, but should it really be this difficult?  It is not self-explanatory in the least, and I can't find a single source of good information on how to get this set up.  I am glad I kept the box, because if I can't get this figured out, I will need to return this, which I'd rather not do since it is working so well in the hardware world and it seems like it should her a no-brainer.

I really hope there is something simple I am missing.  Any help would be greatly appreciated.

Hello CL, my NDLR is unfortunately defective. First there was no display/menu after the start screen, now it won't turn on at all, doesn't light up etc. How can we fix this? Many greetings! Hubert

2022-11-03
RE: Similar issues with Roland D-550 patch data sysex not transmitting from PC to synth DIN input, as experienced previously with Casio CZ-101

I just recently received a new HRC 880 and have been putting it through tests with old synthesizers.

Bottom line, up front: I am generally pleased with the HRC 880 - it fills a need for "desktop lab" interface at an affordable price point. Thank you, Conductive Labs. Through testing, I have devised an implementation scenario that will work with the 880, despite issues with PC=>legacy synth SysEx transmission.


=== CONTEXT ===
This thread is about tests with a Roland D-550 synth module and the MRCC 880.

Previously, I started a thread in the MRCC 880 forum, entitled "MRCC 880 issue with patch data sysex not transmitting from PC to synth DIN input"

https://conductivelabs.com/forum/showthr...p?tid=2042

That previous thread concerned tests with a Casio CZ-101 synth.


=== D-550 tests - basic CONCLUSION ===
Similar behavior to previous tests with Casio CZ-101: some types of USB PC=>DIN SysEx transmission didn't work, whereas such transmissions worked OK with two other MIDI interfaces.

Transmission of single patch data from D-550=> PC worked fine, no matter what MIDI interface was used.


=== ENVIRONMENT ===
* Hardware - Roland D-550 synth module, MRC 880, Mac mini computer
* Software - macOS 11.7, Patch Base patch editor/librarian, Logic Pro, MIDI Monitor, SysEx Librarian


=== DETAILS ===
This testing concerned receiving and transmitting single D-550 patches. Single patches are what I will be dealing with primarily in patch editor environment, so that was the focus of the tests.

So observations concern SysEx composition/behavior of D-550 patch dumps. (Didn't attempt bulk dumps in this test, but have done so successfully with other MIDI interfaces, in the past).

Routing:
1. Tested first with MRCC 880
* DIN MIDI OUT (D-550) to PC USB IN and
* PC USB OUT to DIN MIDI IN (D-550)

2. Then tested with E-MU XMidi1X1 (simple USB to MIDI interface)
* E-MU MIDI interface connected to PC via the E-MU's USB port => to DIN port 1 (in/out)
* MRCC 880 powered by 5V DC power, independent of PC
* D-550 to DIN port 2 (in/out)
* DIN IN 1 => DIN OUT 2
* DIN IN 2 => DIN OUT 1


=== D-550 SysEx: OBSERVATIONS and CONCLUSIONS ===
1. In all programs, on all MIDI interfaces tested: D-550 => PC single patch transfer worked as expected.

2. On dumping a patch to PC (or the other way around), the D-550 was observed to send 468 bytes in two chunks:
  - 266 bytes
  - 202 bytes

In SysEx Librarian:  
You can save these SysEx chunks as two separate SysEx files and send them successfully, in tandem, PC => D-550, to populate D-550's temporary patch memory.

This works no matter which MIDI interface is used, presumably because there is a pause between transmissions (?). Not necessary to adjust "Transmit Buffer Size" (as with the CZ-101) or "Pause between played messages" parameters: works fine in default values.

A single file of 468 bytes (as saved in Patch Base) - byte for byte identical to the two "chunk files" - didn't successfully transfer from PC => D-550, on any MIDI interface tested, with SysEx Librarian. One can hypothesize that this is because some sort of pause is required between the two chunks that have been combined into a single file, and SysEx Librarian doesn't know that is necessary (?). But again, I have no actual idea.

In Patch Base:
This is interesting. Patch Base can save the patch SysEx as a single 468 byte file. This file, when sent to the D-550:
- with 880: DOESN'T successfully populate D-550 temp patch memory (aka, doesn't create a different sound)
- with other MIDI interfaces: DOES

In addition, when Patch Base sends a single parameter change to the D-550, it sends 11 bytes (the CZ, by contrast, dumped its entire patch memory on every param change). But the important thing: this small PC=>D-550 transfer "works" with whatever MIDI interface. 

So, as was the case with the MRCC 880 and CZ-101, *some* types of (typically small) PC=>synth SysEx transfer work fine. Generally speaking, the short handshake and param change transfers work, but when it comes to larger chunks, conclusions are more complicated. 

I showed above, for example, that SysEx Librarian was able to successfully send patch data from PC=>D-550 by breaking into two separate chunks (files) and sending in tandem, with default 100 msec pause between - and this works with whatever MIDI interface. 

Patch Base, otoh, sends 468 bytes together - unknown if there is a pause between the two chunks of the message, but the developer apparently knows how to account for the particular SysEx composition of D-550 patches: this transmission works with other MIDI interfaces, but not the 880.

So while using the program with MRCC 880 directly connected to PC, small 11 byte param changes get through to the D-550 -- and are reflected in its sound changing, for that parameter -- but loading a full 468 byte patch from hard drive doesn't get through.


=== P.S. ===
After testing CZ-101 with MRCC 880, there were four (4) more potential legacy devices to test.

I tested one more, the Roland D-550, and that is enough.

It is possible to devise an implementation scenario, now that I know what generally works and what doesn't with older synths. While it is disappointing that 880 PC=>synth transmission didn't always work, with every program in every context, in my case I probably don't want the 880 to primarily interact with a PC directly, most of the time; it's as valuable, if not more so, interacting with other interfaces and devices strictly through DIN ports.

In the process, I did a lot of reading. Issues faced with individual MIDI interfaces, SysEx, and older synths are not unusual. 

Have read accounts of D-50 and D-550 also having transmission issues with particular interfaces. The MIDI synths I have been testing recently are 30-35 years old, in some cases. I have one synth (Korg Poly 800) that was released before MIDI spec was fully finalized, and it had to be retrofitted to enable it to even send/receive SysEx bulk dumps. Prior to that, the Poly used and can still use FSK (audio) data dumps for patch sets, even though it originally had MIDI ports which worked fine with program, controller, key on/off, etc.

So in context, all is good. thanks.

I'm having a few effects pedals (Chase Bliss, Empress, Hologram), which are all MIDI-controllable., I'm not new to this: But, with the Chase Bliss pedals I have no luck when it comes to the MRCC. I'm using a MIDI-to-TRS-B-cable which works absolutely fine, when I connect the pedals directly to an Elektron Digitone, Digitakt or AKAI MPC One for example. Also when I'm using a MIDI-TRHU-port of the ASM Hydrasynth, Microcosm or even a passive MIDI-Splitter like MIDI Solutions Quadra Thru V2, the Chase Bliss pedals do, what they are supposed to do, except with the MRCC. Attached to it MIDI won't work at all. To me it looks like something essential for those pedals is filtered out by the MRCC. Any ideas?

Is MRCC protected from invalid midi cable connection (MRCC OUT to Synth MIDI OUT)? I use MRCC to provide midi clock for few other jam members via midi cable. What if somebody will connect midi cable to MIDI OUT instead MIDI IN? Will MRCC MIDI OUT survive input signal from another synth/controller? Any dangerous?

SUBJECT: 
MRCC 880 issue with patch data sysex not transmitting from PC to synth DIN input

Using Conductive Labs MRCC 880
rcvd and tested 2022-10-29


ROUTING:
On the MRC 880, I have the routing set up correctly for
* DIN MIDI OUT to PC IN and
* PC OUT to DIN MIDI IN


=== Testing with a Casio CZ-101 synth ===
SUMMARY:
* DAW and CZ-101 work as expected when transmitting/receiving note/controller information, using MRCC 880

* PROBLEM: sysex from PC to CZ-101 not transmitting successfully in Patch Base patch editor application using MRCC 880, whereas this operation works perfectly with a simple USB to MIDI IN/OUT adapter


ENVIRONMENT:
* Hardware - Casio CZ-101, MRC 880, mac mini
* Software - macOS 11.7, Patch Base patch editor/librarian, Logic Pro, MIDI Monitor


DETAILS:
Have confirmed the following by using the macOS app "MIDI Monitor" and including in its Sources preferences "Spy on output to destinations" => so in effect, the app will display data going *into* and *out of* the PC

1. In the Patch Base app, I can use its virtual keyboard to successfully send Note On/Note Off to the CZ-101, and that data is reflected in MIDI monitor's data window. Just like a DAW, in that respect.

So, notes can be successfully routed to the CZ-101 DIN input from PC, using the MRCC 880.


2. I can use Patch Base's "Fetch" icon to successfully transfer the CZ's current patch to both MIDI Monitor app and Patch Base app -- 264 bytes of sysex -- and I can examine that data in detail in MIDI Monitor app. This is the sysex for 1 CZ patch => so sysex transfer from DIN output to PC input is working as expected.

To perform the dump from CZ to computer (initiated from computer), a dump request is first successfully sent from PC output to CZ DIN input (10 bytes): F0 44 00 00 70 10 60 70 31 F7.

=> So, at least *some* sysex is getting through to CZ DIN input from PC, just not patch data itself.


3. I can load a new patch in the Patch Base editor, from hard drive, and it will successfully populate the app's editor window (per usual) and its data will be reflected in MIDI monitor's data window as being sent to output destinations.

Doing so SHOULD automatically then update the synth's temporary patch memory to the new patch. It DOESN'T, when connected through MRCC 880; it DOES work when connected via a simple USB to MIDI IN/OUT adapter. This is consistent behavior, across many tests.

I can then make a change to the patch in Patch Base, and a complete batch of 264 sysex bytes will again be reflected in MIDI Monitor window, with each change -- i.e., the patch editor is dumping the entire patch's sysex to CZ, on each change. Again, such changes to a patch on the PC are NOT reflected in the synth's temporary patch memory, so no data is apparently getting through to the CZ.

During this operation, I can set the MRCC 880 to "MIDI Mon" and see a brief flash, so apparently something is coming into MRCC; but in any case, data is not then transferred successfully to the CZ-101, no matter which MIDI IN DIN port it is connected to.

- - -
Don't know if a firmware update can address this issue, but as of now, the new unit is not working as expected. I tried lowering the MIDI transmit speed to MRCC Ports in Patch Base -- no joy, same issue.

Thanks for any help. There is nothing on the forums I can see about this issue - nothing much yet about the MRCC 880, in general, as it has just been released.