So I’ll start by saying I’m totally new to Morningstar, but I’ve navigated complicated switching systems in the past via midi so I’m not a total dumb dumb turkey.
I need to really fiddle around and get comfortable with my new set up before I do much complex stuff, so my idea to start was to choose 6 pedals (loops) that I want to toggle on and off with the MC 6 Pro-- essentially a stompbox style setup.
I created a preset in the ML 10x with all six loops inserted and engaged. My plan then was to have six different presets on the MC 6 Pro, each that toggles on/off it’s specific loop. The preset on the ML 10x would never change, but pressing the button in each of the MC 6 presets would engage or disengage one of the loops. I’m pretty sure I did everything correctly, I have the ML 10x Midi In connected to the trs Midi Out of the MC 6 Pro, I have my ML 10x set to midi AND device id channel 3, on my trial preset I tried sending both native and midi (cc) messages with the correct output channel selected, respectively and literally nothing happens.
I have tried disconnecting both devices from the editor in case it wouldn’t output midi while connected to the editor, still nothing. I’m at a loss, and I bet I’m just missing something dumb. As I said I’ve tried making this preset work both with native support and via midi and I’ll post a screenshot of each version of the preset here so you can hopefully tell me what I’m doing wrong.
In your first screenshot, both messages are in “Pos: Both” which means that both messages are being sent at the same time with each press. That means that the ML10X will receiving the CC#26 value 0 first, and then the CC#25 Value 127 immediately after. So the ML10X will only always engage Loop D Tip, since value 127 is the last message received.
Sounds like you want to toggle between the two messages instead. If so, then you should set Msg 1 to “Pos: 1” and Msg 2 to “Pos: 2”.
Regarding the second screenshot using the ML10X message type, can you let me know if there are any other MIDI Devices inbetween the MC6 and ML10X? Some MIDI devices do not pass SysEx messages through (like the HX Stomp and Microcosm), which is essentially what the MC6 PRO is sending.
I’ll try to change the midi patch, but I’d definitely prefer the ML 10x Message type. Initially there was an H9 in between the devices, but when it wouldn’t work I just hooked the ML 10x directly to the MC 6 Pro to rule out things like what you mentioned. Would love to figure out what isn’t working.
Ok update- I tried your suggestion for the midi version of the patch and it’s still not working here either.
At this point the ML 10x MIDI din5 is hooked directly to the mini trs out of the MC 6 Pro, and whether sending the midi cc changes or the ML 10x message type absolutely nothing is happening on the ML 10x
OK- so I confirmed it was a type B adaptor so that was one issue. Connected directly from din5 out to din5 in, I was able to make the midi CC commands and the ML 10 x commands to work!
Ok so the latest is- if I directly hook Din5 out of MC6 Pro to Din5 in of ML 10x it will work, but miniTRS out to Din5 in is not working, and yes I did replace the type B adaptor with a type A. It seems like the miniTRS is the issue here. The MC6 Pro should be sending the same message out of both midi ports correct?
