MIDI doesn't produce sound so I'm not sure how this applies:

it appears that the ESP VST is blocking MIDI from going out from the VST into GP5.

I imagine MIDI is supposed to be sent from GP to the VST and then you would expect audio (not MIDI) to be generated by the VST. 

I don't have ESP - maybe someone else can help.  But isn't there an indication on ESP that Part(s) are producing output?  Meters that go up and down (from the "home" screen)?

If so, and you see this activity then you would know MIDI is reaching ESP.  If not, then there may be a routing issue.  If you see the meters dancing and no sound then you have to validate the audio output of the VST is properly setup. 

It would be good to cut the problem in half like this and continue with a focus on the input (MIDI) or output (audio) side.

Post ALL of the configuration details of your PC, DAW, gig performer and ESP.

it appears that the ESP VST is blocking MIDI from going out from the VST into GP5.

The ESP uses Montage M Port 4 - have you configured it to use that port instead of 'Unassigned'?

How have you configured gig performers' omni midi block? You need to connect it directly to the ESP plugin block

Open the midi block and verify the channel being used. 

What pc os and version are you using? What daw are you using?

If you are using windows what version? On windows only one app can have a midi port assigned so it the port the esp needs is already assigned to another app it can't be used by ESP.

Does your ESP work with your Montage M?

Has your ESP ever worked with any DAW?

The configuration is the most likely cause of issues but you need to provide the full details. If GP5 opens port 4 the ESP plugin won't be able to use it. If that is the case you need to find the port 4 entry in the Midi input ports section and uncheck it. Then close GP5 and reopen it again and verify that it is not automatically opening the port 4 again.

Posted by: bryan

↑

I spent about 3 hours on a zoom with the creator of GP5

Yeah, I'm that creator 🙂   Turns out the problem had nothing to do with ports. A couple of days later, on a whim, I asked and discovered that customer had checked the Run under Rosetta box for Gig Performer. Consequently GP was running as an Intel app.

As soon as he unchecked that Rosetta setting, the plugin worked perfectly.

The problem is completely solved. 

Stellar customer service.  Thanks for reaching out.

The problem is completely solved. 

We appreciate you taking the time to provide an update. Yamaha just released new OS updates for both the Montage and Modx M models and a new ESP version to match them.

So with all the changes going on, and an impending addition of MIDI 2.0 functionality, it isn't always easy to know how to troubleshoot configuration/version issues.

Not that you don't have enough on your plate but a MAJOR addition to MIDI 2.0 is CI - capablity inquiry. That provides the ablity to 'programmatically' determine what an instrument is capable of: what functionality is/isn't present.

Don't know what would be involved to provide a small utility for your software that can do a 'sanity check' after being installed to make sure it has been configured properly.