If you want to know what functions in MIDI Guitar2 are assignable, click first on the INTERFACE button in the upper left corner, and then the MIDI LEARN button in the MIDI interface box. If you do that with your Custom Gate script loaded, you can see that there is nothing assignable there!
So the way to go about things is to make two identical patches, but where one has the custom gate and the other doesn’t. Name them 001, 002 for instance, and set your footswitch to send out Program change (PC) messages. You can now turn custom gate on and off with switching between presets instead.
I thank you, LoFiLeiF! But this option does not suit me, since the download speed of the new preset in the “Live mode” mode (8 different instruments) is 2-3 seconds (+ you need to click on the footswitch itself many times), which is very inconvenient. I still want to know if there is another way to turn on and off “My midi machine” (Custom Gate) using footswitch? Perhaps this can be done at the script level in Custom Gate?
I use MG standalone for live performance and change patches using a MIDI controller via a Program Change message. Works fine, but I’m limited to 128 patches as PC values have to be between 0 and 127. Is there a way to increase this, eg the equivalent of Bank Select before sending the PC value? I don’t want to wrap MG inside a DAW as I"m trying to keep the CPU/RAM load as low as possible for reliability when playing live.
A DAW is not a very practical piece of software for playing live anyway, and, as you said, it uses a lot of unnecessary resources in that case.
You should rather use the MG plugin in a plugin host which has many advantages: it uses almost no resources or memory other than the plugins it hosts, it is optimized for live performance, it allows you to play with as many virtual instruments and effects as your computer allows, there is no limit to the number of global presets that can be recalled by your midi controller, etc.
Thanks @Herold, I’ll try Element in the first instance - at first glance it doesn’t seem to have a huge amount of documentation, but might be a good thing as it’ll force me to try and understand what’s happening under the hood!
@CharlieFarley Have you seen the documentation? It seems to be helpfull: Manual
I had a quick look at Element, I saw that there was an active forum with lots of questions - as for MG - and there are also several tutorials on youtube that should get you off to a good start: Element tutorials
Thanks @Herold, I’ve been through those documents and have been able to set up a plugin chain, route audio and MIDI, map MIDI controllers etc so I’m getting there. I’m still not sure about a few key things like workflow etc but early days yet. The documentation isn’t as comprehensive as say Gig Performer and the forum not as slick as Jam Origin, but entirely understandable as the developer/s of Element make it available for free and doubtless have huge demands on their time. All credit to them.
