If that's what you mean, where's the problem? You might not want the global block to stay global in the new preset? If so, there would be two solutions:
- Remove the global block and add a normal block instead (you could use a Favorite or User Defaults here).
- There could be a way to "un-global" a global block.
This is possible with the GT. But it's cumbersome as you'd have to check each and every block for being global or not. And once you forget one, chances are you'd mess up other patches. Take a wild guess of how I know...
Well, that sounds like a really niche use case, to be honest. Sorry if you've mentioned this before, but, what would be the solution you suggest in this case?
Using global groups, as described.
Once you copy a patch you would have to explicitely tell it to become a part of that global group again. Which would possibly be a 1-2 click affair.
And well, as far as "niche use case" goes: Have you ever tried adjusting the relevant parameters in a patch through some external MIDI knob/fader box? I have, and it's absolutely excellent. I'm even considering to buy one of
these here, should the Stomp make it back onto my main board (which may happen).
And IMO one of the reasons we don't see more people doing so is the lack of global blocks, simply because once you switch patches, your external knobs/faders won't represent the actual values anymore.
---
However: There's another reason speaking against your proposal. With that proposed favourite-alike list of global blocks, you might add one of those global blocks to a patch. Fine.
But how would you know in which other patches that global block is used? Right, you won't know at all. This is one of the big issues of the Boss way. My mind might be able to keep track as much as in "block presets 1 are for live preset bank 1, block 2 presets are for live preset bank 2" - and that was it already, especially as you might use multiple global blocks of the same type (in my case delays and EQs). It's incredibly tough to keep track of that once you have a larger amount of banks all using different global block presets. I'd say it's almost impossible to run this 100% error-free, especially with an ever growing list of patches and live sets.
You have to be very careful with that, and try to keep things as simple as possible.
My proposal would be very easy to use. And pretty much foolproof.
Just add the patches you want to use for any given gig to a "global group" (could as well just be a setlist - this is where we could debate about how this could interact, or rather shouldn't, etc.) and decide which of the blocks within a patch of that group should become a global one.
You could possibly start with, say, a clean amp and set a checkmark in whatever "global" (or rather: global-group-wide) box. In any other patches assigned to that very group, this amp would now be available to pick from whatever menu. In that very menu you wouldn't be able to pick anything else but that very amp (or anything else that you've assigned to become global).
And that's pretty much it.
And as far as organisation goes: Once you copy a patch, you'd have to explicitely select a global group again to keep it inside that group, a plain saving process would create a "normal" patch. No hassle at all as selecting a global group would be a one-click affair on the saving process.
In addition, all patches belonging to a global group should be indexed in the patch list, just a color and a number from, say, 1-10(0) would be fine, depending on how many global groups you allow for. For my personal use case, 10 would be absolutely sufficient, especially in case the overall process of assigning things is easy. Too much and it'd possibly become too confusing.
As said, this should defenitely *not* be another, extended way to present block presets (which is what it's handled like in the Boss universe) but a "strictly live" utility. Something that should be as easy to add to any existing setlist/bank as it gets.
Maybe if I understand your use case I could change my mind,
Don't know how to explain it any better. As said, this is pretty much strictly a live (or let's call it "realtime") playing functionality. The home dweller may not ever need it (unless you're mimicking a live performance). I wouldn't even call it a "feature" but rather a "utility". This hasn't got anything to do with block presets or whatever (that functionality is covered already). It's single purpose would be to adress the "Yuck, my cleans aren't loud enough but I don't have enough time to adjust and resave all of my 13 clean patches during soundcheck!" issues.
It'd take you one step closer to re-create a complexed hybrid, loopswitcher-controlled rig. And as said, these are the rigs I enjoyed playing the most. Not because of their sound but because I was able to quickly tweak the entire setup in a matter of seconds to accomodate pretty much each and every situation.
Almost needless to say, but: it might as well become very handy for some other scenarios. Let's say you'd use a "free form" patch that you'd call up here and there. You have that nice MIDI fader/knob box (or a virtual representation through, say, TouchOSC) sitting there already and start some delay mayhem on that free form patch. Now you switch back to one of your bread and butter patches. Call up the free form patch again and your delay will be back to it's saved settings, not corresponding with the dialed in knob controller anymore.
After all, there's a reason for me going back to a hybrid setup and using the only unit on the market doing global blocks (namely the GT-1000 - ok, there's the Axe FX III as well, but I can't justify the huge expense only to end up with a rack unit, something I just don't want to deal with anymore). I'd rather not have to do so as I'm absolutely fine with anything the HX-verse delivers soundwise.
![[Nathan]](/data/avatars/m/0/613.jpg?1726885163){kind=avatar}
