MC6 Pro on 3.12 Not Responding to MIDI IN Messages (Resolved - Not a MC6 Issue)

Hi. Not tagging this as a bug in case it’s me, but I’m very experienced with this stuff and this is driving me crazy. My MIDI chain goes like this:

Disaster Area MIDI Baby 3 → MC6 Pro → GigRig G3 → various pedals (all with 5 pin DIN cables)

I’m trying to use the MIDI Baby to change banks on the MC6 Pro and also do tap tempo for my delays while setting the MIDI clock on the MC6. The tap tempo button sends messages THROUGH the MC6 to my delay pedals just fine, but the MC6 seems to be ignoring CC 8, which from the manual should set the MIDI clock.

Additionally, the other two foot switches are sending CC1 and CC0 to bank up and bank down respectively. MC6 doesn’t seem to respond to this either. The MC6 screen does show the blue I icon when I press the buttons on the MIDI Baby, so it seems like it knows something is happening, it’s just not handling them.

I’m not sure what info I should provide that might help, but will provide anything requested. All of the MIDI channels are set up correctly (channel 2 for the MC6), everything else works, all the messages coming FROM the MC6 work great and it’s clearly passing MIDI through the DIN. Please help!!

Thank you,
Ryan

Just tested (sending CC#0 and CC#1 from an external controller to the MIDI IN port on the MC6P) and seems to work fine. Can you double check the MC6P MIDI channel to confirm it is set to as per the message you are sending from the MIDI Baby?

100% is the same, all channel 2. I even tried changing it all to 16, same result.

I just tried changing to different MIDI Channels but no issues. Let’s troubleshoot further:

Can you try routing the messages to USB device and open the MIDI monitor to check what MIDI messages is the Baby3 sending?
image

Ok, so for whatever reason the MC6 Pro shows the messages coming in as being channel 1:


but the MIDI Baby is clearly set to send to channel 2:

In the editor, go to controller settings >> MIDI channel settings and check for channel 2, whether the Remap setting is set to No Remap?

It’s also worth a try to just change the MC6 to channel 1 and see if it responds to the MIDI baby on channel 1

And when I changed it to MIDI channel 1 it did start responding to the messages, so at least I have a workaround. I’ll have to figure out how to change the Ventris to channel 2. I think there’s an app involved.

That said, I updated the MIDI Baby 3 config to send those messages on channel 1 and now it’s not working again, and I don’t see those messages coming into the MIDI monitor at all for any of the 3 buttons. It only shows the two messages on the tap tempo switch that go to the two delays. So something isn’t right. The MIDI Baby works great with everything else, and I know I’ve used channel 1 on it before because my G3 used to be channel 1.

Just to troubleshoot, if you change the messages back to channel 2, does the MC start responding again?

Do you have another USB MIDI interface that you can connect the MIDI Baby 3 to so that you can monitor the messages being sent from the MB?

1 Like

I swapped the MIDI Baby back to send on channel 2 with the MC6 set on channel 1 and it’s working again, so it’s at least repeatable. I have other devices that can receive MIDI but none with any monitoring options that I’m aware of. That said, let me see what happens when I plug my G3 into the MC6 and send the same messages the MB3 is sending, get back to you shortly

1 Like

Ok, so I tested with the G3 and things worked normally. There definitely was something wrong with the MIDI Baby 3. It completely went past me that their editor also has a MIDI monitor, and it confirmed the outgoing messages were wrong. So weird that it was just the two channels that were messed up and no idea what happened since it’s a pretty basic config. Anyway, I sincerely apologize for the trouble and confusion, but genuinely appreciate the help!

1 Like

I updated the title of the thread to say it’s resolved and noted it’s not a MC6 issue

2 Likes

No problem, thanks for the update! Glad you managed to pinpoint the issue.