[Request] GPE Simult Vs Mute Groups - let the battle begin

In GPE i am making a instrument chromatically, but use simult to play a sound that does not pitch shift. (allows me to key switch a second sound) like for instance fret scrape. Good method i find as i can use velocity switching layer variations in this way, and use this to turn on and off the second unpitched noise, so it can be controlled. Also can use this method to make attack of sound appear then disappear easily. Also set up second simult pad for different scrape or fret noise for second octave, (realism) but still have chromatic instrument sounding. there is so much that you can do here though, I am trying to explain. The upshot is that I am always finding that it is a real shame that the simult and mute groups/pad is mutually exclusive. Mono mode in program will not allow simult pad. cant really do same in instrument.

I can see that it can easily be made to conflict BUT if you set it up right it would be killer.
So I am simply saying that if the behaviour can be done, then why does the state of the mute group and simult actually switches when we switch between them. So if i set up a simult pad, PAD A1 + PAD B2 and also mute PAD A2 with mute group. I can not do both. it does it then ignores it when switching to mute groups. I want the mute groups so simult works in a psuedo mono mode and I can cut of other playing sample which would be in this case another note of my instrument.
yeah so, can it be set up so that the switching between the two does not turn of the behaviour set. So if you set up a mute group it would stay set up even though we haev say changed it to simult pad. Its like we turn of the programs ability to know we have changed that parameter. This insight makes me beleive it can be done programming wise.

I said let the battle begin as the two functions do fight each other, and they should work together in peace and harmony IMO. not wanting a flaming

It's setup as an exclusive mode. In SIMULT1 mode, the far right GROUP column is still visible. Maybe that could be enabled for allowing a mute group to be set while in simult1 mode.

Currently (MUTE GROUP DISABLED):
[ A01 | SIMULT1 | A01 | A02 | A03 | A04 | -- ]

Request (MUTE GROUP ENABLED):
[ A01 | SIMULT1 | A01 | A02 | A03 | A04 | 1 ]

But the way it's setup right now, the targets all share the same slots. You can see this by setting target1 to "A1" in MUTE mode, then "B1" in SIMULT1 mode, then switching modes back to MUTE. If it were setup independent, then it should remember each setting, but it doesn't, it just has 1 shared target definition area.

It looks like allowing a mute group in simult mode might be more likely to be easy to enable. But it depends on how it's coded. If simult and mutes working at the same time is possible, that whole section might need to be reworked to think of it that way. Right now it's setup thinking that it's only going to allow one at a time.

It's worth asking. It seems useful to use simult and mute at the same time. I also don't like how sometimes the VOICE MONO mode doesn't work. If it's set, it should always work that way.

The old joke goes "It is just a simple case of programming".
meaning nothing is ever simple. even though it seems so.
To me it seems the way to go is to make those parameters change to reflect what is happening in the mute/simult choice. So I think he might be able to not switch behaviours when we switch the option between simult and mute. BUT we do want to see the parameters reflected.

It's possible they can work at the same time, seems like they should be able to, in which case the interface just needs to be reworked. Instead of thinking of it purely as modes, it can just be redesigned to consider it like a tab. So each tab mode has its own settings, and if it's set, then it's enabled.

Then the way it works is, if you don't want MUTE on, you don't set any of the targets or group. But if you do, then you can set the targets, or group, and that enables the muting for that pad. But you can then switch over to the SIMULT1 tab, in the same exact way as you do now, you just don't call it a mode.

Then you can set your SIMULT1 targets, and they both work at the same time. Then if you switch the "SIMULT1" back to "MUTE", all it does is show the targets and group settings for that mode, and when you go back to "SIMULT1" it shows what's set in there. It is workable with the interface it has right now.

But probably, as most features seem to be, it was thrown together for bare necessity, and to set it up to have separate memories and work at the same time would require more work, and JJ developer is always bouncing around from feature to feature. So you'd have to request it at the right time.