I’d like to utilize the MC6MKii along with my MC6 Pro to trigger DAW and related on my iPad.
I’ve got the two working independently, both connected via USB to the iPad.
What I’d like to do is:
Use both independently, as mentioned above
Also, use the older MC6 MKii similar to how I would use an aux switch (not exactly, just similar) for the MC6 Pro…ie: To use the MC6mkii to Bank up/down and page up/down on the MC6 Pro
To do this, I figure I have to run the mkii into the Pro and then enable midi through to the ipad from the Pro.
I’ve tried using a midi cable and setting cross midi thru on the MC6 Pro with no luck (not sure why the setting was never showing as saved tho, I tried numerous times).
Also, trying now with a TRS cable in the mkii expr 1 and the Pro’s Omniport 1.
I tried changing the Omni port 1’s setting to standard midi A.
Finally, if I can get the above working, I’m wondering if I can power one of the morningstar devices via the other using the power capability of the TRS cable.
It’s a HOSA balanced interconnect 1/4 in TRS cable.
I’m by no means an expert, however you can assign a channel number to each Morningstar controller and the dictionary has a list of the different cc#'s that control functions for each of those controllers. Therefore, it stands to reason that you should be able to set this up in the editor.
Hi, the above isn’t advisable. Those ports are midi out/expression in only. That won’t work and can potentially cause harm to the controller.
I’d try to connect the mk II’s usb port to the pro’s host port. The host port should be able to deliver enough current to power the mk II. Make sure that the pro is powered by a supply that delivers enough current for both devices, though.
@GuitarWolf, connecting the mk ii’s usb port to the pro’s host port is working, thanks.
I am wondering about a few things in case you/others can help:
The mkii is reacting to the cc messages sent by the pro, but I don’t want it to…what specifically to update in settings (and pointer to how/where please) to avoid this, do you know? I read the docs, but was unclear how I can tell mkii not to listen for incoming midi on certain channels or certain parameters, so that I could avoid it erroneously receiving messages that go out from the pro device to the ipad, which appear to be received also by the mkii
when sending midi via pressing switches on the mkii, the source device is showing up as the pro on the receiving apps on the iPad, since the pro is passing the mkii’s messages through…I’ve changed the messages from the mkii to come from channel 2 (and the pro sending on channel 1), so there’s no conflict/confusion from the apps, but is there a better way to set this up so that the receiving apps can actually display the mkii as the originator of the messages, so it’s easier to create/edit settings on the receiving apps, since I can more easily see what’s what…actually, this is quite important as some apps not only “learn” the cc# and value but also the device that is sending…so with the current scenario, I cannot test the mkii midi switches unless it is daisy chained through the pro and it’s much easier to be able to connect the mkii directly to the ipad in order to edit its presets and have the apps “learn” the midi, but then be able to connect the mkii into the host port of the pro when actually playing live, so that it can also send midi to the pro in order to bank up/down and page/up down as I’d like
Hi,
to prevent MIDI loops you should go to ‘controller settings/general’ of the pro. Disable MIDI through from device to host port. This should stop the pro to hand down messages to the mk II which come from the I pad via the device port. The usb connection is bi-directional, so be aware of MIDI loops in general.
If you don’t send messages to the I pad on the channel you’ve chosen for the mk II you should be fine otherwise.
Just to clarify, if you set the MIDI channel (Rx channel) of a device it will only act upon messages it recieves on that channel.
It is sometimes possible to set also a general channel for the transmission (Tx channel) of messages on some MIDI devices, but that is not how the MC works.
The pro acts as a MIDI interface in your setup. That’s the reason your software can’t see the mk II. You’d need a separate interface to which both MCs can be connected to, to be able to make a distinction between both devices.
Thanks @GuitarWolf. Is there a hub setup where I can:
a. connect the pro and the mkii so that they both are directly connected to the iPad (this I can accomplish with the usb dongle I currently have and would allow me to easily switch the morningstar editor between the two of them) AND
b. have the messages from the mkii received by the pro to bank up/down when I explicitly want that to happen
You’d either have to have a software by which the MIDI can be routed or use a midi interface that can do that for you. What usb dongle are we talking about?
Can this power your mk II?
You could just use the 5 pin in/outputs of the MCs to establish a direct communication, while being connected to the I pad via the dongle.
Just be aware of MIDI loops.
Yup, it powers both, but I also have a power adapter I can plug in to the mkii just to not draw so much from the iPad.
So, you are suggesting direct connecting both mc6’s to the ipad via the dongle and also have 5 pin midi out of the mkii to the 5 pin midi in of the pro, ya?
What settings would I need to adjust to have the 5 pin midi in to the pro not sent out to the iPad?
Thanks @GuitarWolf, but if MIDI thru and midi cross thru are both off, does it matter what checkboxes are on/off in the various midi channal boxes below?
This area of tbe UI confuses me, since I’d expect those channel areas with the checkboxes to be grey’ed out if midi thru and midi cross thru are not on, but that’s not the case.
Are you using the beta editor?
You can disable midi through and cross midi through on the mk II. There is no option to select specific outputs.
For the pro you’ll have to select the through options manually. There is no option to turn off midi through globally.
I’d disable midi through and cross midi through on the mk II and in addition to that midi through from the 5pin to usb on the pro.
This should prevent possible loops between the MCs and the I pad.
Not using a beta editor afaik, certainly not intending to. Am using the editor on the iPad, fyi.
That’s said, i do see a global setting for midi thru in the Pro settings, here is a screenshot
That looks like the editor for the mkII.
I use Android or Windows, can’t tell for sure, but it looks like the midi through settings for individual ports are missing, too.
Is your app and mc firmware up to date?
That’s odd, I’m explicitly selecting MC6 Pro Port 1 (I see MC6 Pro Port 1, MC6 Pro Port 2, MC6 Pro Port 3 and MC6 Pro Port 4 options) and pressing the connect button when editing the Pro, but I’ll check the firmware and update options…surprised the device or app wouldn’t flag an issue/incompat if there was one happening. Thanks for pointing this out
