GP, Morningstar MC6 and MIDI Guitar 3 misbehavior

I have a problem. In Gig Performer I’ve set up 10 rackspaces, each loaded with an instance of MIDI Guitar 3 set up the same way, using the same preset, that each triggers a different virtual instrument. Those 10 rackspaces are mapped to a Morningstar MC6, with the 6 buttons of the MC6 first bank mapped to the first 6 rackspaces and the first 4 buttons of a second bank mapped to the remaining 4 rackspaces.

When I switch between rackspaces in the first bank, in any way, all is fine. It works well. The problem is that when I go to the second bank and switch between rackspaces, the MG3 preset changes. It changes to another preset, so things don’t work anymore. No matter how many times I switch it back to the right preset (which again is the same as the one used in the 6 rackspaces of the first bank, which works fine) when I switch between the rackspaces mapped to the MC6 second bank it changes again.

S, I’m at a loss. I tried all I could and nothing works. And I triple checked everything—on the MC6, in Gig Performer and MG3. All is set the same everywhere. The only difference from one rackspace to another is the command in the MC6 associated with each switch, which is simply a different PC number corresponding to the rackspace number. There is nothing else happening, no difference at all in the settings everywhere, apart from that change of PC number in the MC6 to switch rackspaces.

One curious thing is that when I manually click on my Macbook’s trackpad to switch between the 10 individual rackspaces, it all works fine. Then the MG3 preset stays the same. That tells me that the problem is possibly on the side of the Morningstar MC6 (and I left a message in their forum, and in MG3’s forum too), but I thought I’d post that here too, since one never knows…

A picture of rackspaces where this works as expected and doesn’t work as expected would be helpful in diagnosing the issue. My gut tells me that you’re going to need to filter out the bank change message coming from the MC6 into the midi input that is going into the Midi Guitar 3. Also note that according to the Jam Origin website, Midi Guitar 3 is still in beta. This may also be a Midi Guitar 3 issue. Have you reported the issue to Jam Origin?

X

1 Like

Xpansion, I’ll respond to you since you had the kindness to drop by. It’s actually solved, and by a JamOrigin member on their forum. It turned out to be a one-click-solution on a setting in MG3 whose function I was not aware of (No MIDI Controller). While I’ve been using MG for years, I’m still pretty new at all things MIDI. And we learn.

I’m glad you got it figured out. I’m considering investing in Midi Guitar 3 when it is released.

X

I’m glad too—phew. MG2, that I used for years, works well too. As for the Beta MG3, so far so good. It’s now a surprisingly deep, rich program

Please post the screenshot of that option here, so other readers can find it easily.

1 Like

Thanks npudar—you’ve beat me at it.

That said, “No MIDI Controller” raised other issues. One was that I had to add a “MIDI Device” in MG3 to be able to connect an expression pedal via CC#11. Which works fine. Now my next issue is figuring out how to add a sustain—using either another expression pedal I have or a Boss FS-6—so that I can sustain chords with some software instruments to solo over them. I’m looking at how it can be done in MG3, while I’m also looking for that here. I came across a Script (or scriptlet?) someone posted that looks like it does for that, and I’ll experiment with this too. Or there’s an even simpler way which I’m not aware of.