Ipad Controller via TRS midi WIDI Jack

I have searched around and I might be trying something that isn’t possible, but logically I think should work, so I am appealing to the community for some assistance.

Current setup:
DIN5 cabling loop:
MC6 Pro (midi Ch 1) → Guitar FX 1 (midi Ch2) → Guitar FX 2 (midi Ch3) → Guitar FX 4 (midi Ch5) → Guitar FX 5 (midi Ch6) → MC6 Pro

Omniport
Omniport 1 → Guitar FX 3 (midi Ch4)

This works great - no issues.

I got the idea that I would like to add a WIDI Jack to the TRS midi ports and hookup my iPhone/iPad to let me get some more granular control of the midi parameters on my pedals (I am using MIDI Designer Pro X). This is where I am stumbling.

Using the editor I have updated the Controller Settings end enabled the following on the MIDI THRU settings:

3.5MM MIDI In - Thru To = Omniport and DIN5

But no luck. I can see the logs on the midi controller software that the correct CC and values are being sent over the right channel (CH 2 for the testing I am doing). I also see the WIDI Jack blinking indicating it is receiving the data. However, no messages in the editors MIDI monitor or expected results.

Am I missing something really basic like - MC6 Pro doesn’t support this type of use case (or I can’t use the DIN5 and TRS 3.5 ports at the same time)?

If you got this far - thank you for reading and for any assistance. Happy to provide additional details that might help clarify.

Did you only test this with the editor’s midi monitor? There have been issues lately. The midi monitor didn’t work. I think this has been fixed. You might need to update the app.

Hi - thanks for the reply - yes the editor, firmware and WIDI Jack are all up to date. No output at all in the midi monitor from the TRS/WIDI Jack. All other messages are monitored as expected (ie via DIN and omniport).

I’ll plug in a a hardware controller via the TRS midi and send a couple simple CC commands to try and troubleshoot further.

I appreciate the response.

Problem solved. I purchased a malfunctioning WIDI Jack. Luckily I had a second one to troubleshoot with.

Everything is working as expected now.

1 Like