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, that each triggers a different virtual instrument. Those 10 rackspaces are mapped to the Morning star MC6. The 6 buttons of its first bank are mapped to the first 6 rackspaces in Gig Performer, and the first 4 buttons of its second bank are mapped to the remaining 4 rackspaces.
When I switch rackspaces in the first bank, in any way, all works well. The problem is that when I switch to the second bank, the instances of MG3 (which are set up the same way as in the first bank, with the very same patch), don’t stay the same. They switch to another patch, another window with other settings, so they don’t work anymore. No matter how many times I switch them back to the right patch, which again is exactly the same one used in the 6 instances of the first bank, which works fine, they keep switching to another patch.
So, 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—and 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 in the PC number in the MC6 to switch rackspace.
One curious thing, and maybe a hint in the direction of what the problem and solution may be, is that when I manually click on my Macbook’s trackpad to switch between the 10 individual rackspaces, it all works fine. Then the patch I use in MG3, which the same in all 10, stays the same.
Like @Dutti67 said, first confirm exactly what data your controller is sending via a MIDI monitor. I’m assuming that each button is sending a single MIDI PC message to Gig Performer, so it should be simple to observe.
Now, hopefully, you’ve ruled out faulty programing.
There’s another thing though. If I understand correctly it sounds like MG3, which you have placed a separate instance of in each of your 10 rackspaces, is changing presets internally.
That leads me to believe that MG3 is responding to program changes. Try deactivating the MIDI input as shown below and saving this in your patches. It would also be a good idea to confirm that this works correctly in the standalone version of MG3. I can’t say with 100% certainty, but I think this is likely the problem.
BTW, Are you on macOS or Windows? And which beta version of MG3 are you on?
MacOS, latest version, with latest MG3 version, and latest MC6 firmware.
“No MIDI controller”. It will still receive messages from the MC6?
Standalone version. How do I tie that with the MC6 and GP5? I don’t follow.
“MG3 is responding to program changes.” It does look like, but there are no PC in the MC6 tied to its switches other than a “Press” and a different PC number for each that correspond to the different rackspaces in GP5. I tripled checked that.
Yes, each button is sending a single MIDI PC message to Gig Performer. As I wrote, a simple change of PC number matching the rackspaces in GP5.
A MIDI monitor… I’ll check if I have one, if not, I’ll find one somewhere. OK, I do—MIDI Monitor app. So let me check what happens there… And yes, MG3 is changing presets internally. That’s the problem.
I have no knowledge of how to interpret what I’m seeing from the MIDI Monitor. I attach a picture. I can see that it went from 1 to 6 as I pressed the 6 switches and changed the first 6 rackspaces. So far, so good. Then, interestingly, the 1st switch of the second bank (#7) works fine, it switches rackspace with the basic MG3 preset present. But then, that’s where it breaks (second switch/rackspace, #8). If I switch back to the 1st switch/rackspace (7), it still works. Try 9? It breaks. And both times it broke, it switched to “Factory/Guitars/Edgy Guitar”, rather than stay on my, for now, very basic MG3 preset, which I also attach.
Vaultnaemsae, “No MIDI Controller”. That was it, simply. After spending hours going in circles. Gee…
If you care to do so, can you explain to me, in a few words, the function or implication of this setting, obviously so essential—definitely in my case.
OK. After all, looks like it’s not entirely solved, since by setting “No MIDI Controller”, though I can now switch between all rackspaces with the MC6 correctly, I lost the connection to my expression pedal which controlled each instrument volume with CC 7.
So, now what… What setting would allow both keeping things working the way they are now, and the use of the expression pedal? Maybe having a look at the MG3 picture I attached of how the preset I use for every rackspace can help.
Maybe – that’s why I’m asking you to test it in standalone and the plugin version. I can’t say how it will function because I’m not running the same version of MG3 as you.
Don’t “tie” it if you don’t need to. It’s just for better understanding of the current issue.
MIDI Guitar 3 responds to MIDI PC (I think since the most recent version but I can’t recall exactly) if it can hear the messages. You don’t “tie” anything to it. Looking at your MIDI Monitor screenshot, you have a bunch of Sysex flying around but that shouldn’t do anything. The MIDI program changes are sending on channel 2. It’s probably a good idea ro check your GP5 settings regarding MIDI PC reception.
OK, so you need to block the PCs from reaching MG3. I’d need to see how you have GP5 configured to say for sure how you should do that. MG3 listens to MIDI independent of the DAW’s routing, in some cases. A forthcoming version will address this.
Since you asked so nicely… it blocks the reception of MIDI from external sources.
Yes, I was only suggesting this as a test, not as a solution. Some beta testers are working on this with the dev. It’s a little complex to explain since I understand that you’re not too familiar with many MIDI concepts. So, in a nutshell…it depends on how you are using MG3 and there are many ways to do so.
At this stage, I’d recommend to use the “MIDI device” module in your synth chains to funnel in the desired CC#07 and keep the patch bay on “No MIDI Input.” Test this and see if it helps.
Also…operation depends on how many presets you have in MG3. I think someone linked to an explanation I wrote about this in a recent post, maybe one of yours. How many presets do you have saved in MG3?
“How many presets do you have saved in MG3?” While I saved the MG3 preset in each rackspace with the name of the instrument it drives, it’s the same basic preset. So there are many presets, but only in name.
I’ll look into using the MIDI Device the way you describe. On the other hand, it occurred to me that I could just put a slider widget in the global rackspace of GP5, assigned to my expression pedal. I’ll try that too, and it should work. That said, I’m interested in finding out how it can be done from inside MG3.
Back to The MIDI Device, you write "I’d recommend to use the “MIDI device” module in your synth chains to funnel in the desired CC#07 and keep the patch bay on “No MIDI Input.”
How do I do that? So I put a MIDI Device in a chain, fine, and then what? How do I funnel in the CC#?
Also, there is no "No MIDI Input’ in the patch bay, only “No MIDI Controller, USB Device, Morningstar MC6 Pro Port 1 (then 2, then 3, then 4), Any MIDI Controller”.
Please check the exact number in the MG3 folder system.
There are some quirks in MG3 (as a plugin) at present that lead me to use it as pitch-to-MIDI only in this scenario. I would tend to connect MIDI controllers independently of MG3. In GP5 this should be easy to achieve.
Yes. You do it the same way as with the patchbay, but I believe that the MIDI device module doesn’t pass MIDI PC. So. in effect, you’re blocking the PC’s with the patchbay but letting your CCs in directly from the MIDI device module. The MIDI device should see MIDI data the same way as the MIDI patchbay…just draw cables from it to the MIDI Output module.
Sorry, I wrote “No MIDI Input” but I should have written “No MIDI Controller” because I was going on memory. They mean the same thing.
@Bernard: Like you, I use GigPerformer with MG3 (mainly the Hex version) and I had the same problem.
After contacting JamO, I was able to access a pre-release (3.0.63) that solves all these patch management issues via MIDI thanks to new features coming with this new release:
An option to select the MIDI input of the MG3 (Hex) plugin: “Midi Control from DAW”
An option: Sending Midi out to the track to use the MIDI output of the MG3 plugin in VST3 or AU mode.
Automatic detection of the audio interface dedicated to “Hex” mode: GM-800 / VG-800 and others.
This release, which is currently in “Alpha” version, should solve all your problems managing MIDI messages to and from MG3. I don’t know when this release will go into beta… Soon, I hope, because it’s already quite stable.
In this example, I use the Midi Channel 9 to send all Midi commands from the QuadCortex to the MG3 plugin. Midi Program Change commands can be used to select the correct MG3 patch for one GigPerformer Patch:
Notice that it is no more necessary to connect the USB hex audio channels to MG3Hex and take a look to the options: “Midi Control from DAW” and “Sending MIDI out to the track”.
3.0.63 ? I don’t see that anywhere. I run 3.0.62, which seems to be the latest release.
Thanks for trying to help. At this point I’m a bit overwhelmed and quite confused about how to get things where I’d like them to be. While I’ve been using MG2 for years, I’m new to Gig Performer, new to MIDI, new to the Morningstar MC6 and what they can all do. Getting the combination of the 3 of them to work together in a smooth, effective way has been quite a challenge so far. Actually, just getting them to work together, never mind smoothly. While I’ll keep going, and I trust I’ll get there. Patience—patients.
There is no public beta of 3.0.63 yet…read “PRE-RELEASE!”
Until 3.0.63 is publically released, use the method I suggested earlier. For your benefit, I just tested to confirm it works – and it does – so it should get you moving for now.
That’s what I saw—about that 3.0.63. Guess xtian82 just made a simple mistake.
So I finally, at long last, got it to work. This setup now works:
A “MIDI Output” in one chain, set to “Sending MIDI out to the track”
A “MIDI Device” in a second chain, set to “Morningstar MC6 Pro Port 1”
“No MIDI Controller” in the patch bay
The MIDI Output and the MIDI Device are set to CC#11 and wired/linked
That’s it. Now it all works the way I wanted it to work. No more glitch when switching from bank 1 to bank 2 on the MC6—which was the initial issue—and all the instruments’ volume respond well to the expression pedal with CC#11.
Thanks to your generous support, Vaultnaemsae, and everyone else who contributed.
One last thought—for now. While I didn’t try it, I could have set my expression pedal with CC#11 in GP5 using a slider widget, rather than do it in MG3. That raises the question of best practice in terms of CPU usage and overall stability. Which of these two approaches is best? I don’t know. I guess to check the CPU usage I could make make a setup based on the second approach and see what my Macbook’s Activity Monitor shows. As for stability, well, only those who have used one or both of these approaches for a while can say something about that.
