First -- What are you doing that requires that many cues, and at that across two show files? That screams "largest musical ever" to me, and I've done some shows that were honestly too large for that
desk. I generally run out of
MIDI parameters automating Control Changes in
Qlab to make the
console do what I want - rarely Program Changes.
Second -- Flip the thing into Multi-Mode. It's been a few years since I used an M7, but if
MIDI functionality is anything like the CL stuff, you have 2,302 possible Program Change values you can
send out when in Multi Mode, versus Single mode. Just be aware if you have any other show-control that you have made very sure that they won't respond to the Program Changes once Multi-Mode is enabled -- it'll let you transmit program changes across all channels. I find it a little quicker to program than throwing the
console into Bank mode. -- Judicious
tracking of all show control systems is necessary if you have hit the limit and need to transmit in Multimode and have more than one thing that needs
MIDI.
I am rarely if ever a fan of just a generic softy GO
button, especially with their (apparently crazy) number of cues. My issue is that I usually run a main and a backup rig, and need to keep them in sync. In moments of intense
cue firing (generally in tech when you're hopping around), a generic trigger tends to get both machines out of sync. I am always a fan of a discrete trigger - both machines stay in sync, and if one of them misses the discrete trigger, the next
cue gets them back in sync. Plus in tech or put-in rehearsals you can hop around the entire show and things will
track. It's especially important when you have a larger
system - i.e.
FOH Console,
Monitor Console, and
QLab -- discrete triggers from any source guarantee that all desks and playback stay in sync.