Re: crossover in the desk
The scene recall/patch change is a valid point, I was going on the assumption that were I doing this, the Routing/Out Patch would more than likely be SAFEd once set, but I can see how a weekly-changing weekend warrior type setup would be otherwise (my background and desire stems typically from an installed or long-term tour type setup, but I know that a lot of people on here are more along the other method). At that point the only fear regarding that would be a full board reset (or meddling fingers until the security functions are in place)...
I'm not sure what you mean about limiting vulnerability, I'm talking about a direct patch (the one I've asked about before - Routing page -> AES50 tab, set a group of outputs to be a group of "Local" inputs completely bypassing any faders). I do know that this would eat some extra X32 inputs in addition to the standard S16 outputs used (that you would presumably be using to some extent to feed the on-stage crossover anyway), so obviously some adjustments are in order if you need more than 24 local inputs.
I guess I don't quite understand how the power pop is any different this way versus any other way - was this not a concern on analog boards anyway (eg if FoH lost power momentarily while the stage rack didn't, etc)? As well, with your XO onstage, if you had the option to mute outputs on powerup then you had to run to the stage mid-set if the power dropped enough to unmute them anyway, or you could leave them set to not mute (or if your XO didn't have auto-muting) and you'd get the pop anyway, wouldn't you?
I guess I'm out of the loop on this idea, understandably so - my main employment is an installation where all the equipment is in a booth - I've toyed with the idea of moving amps to the stage (to shorten the existing speaker runs by about 120 feet) but haven't had the snake capability to do so, I'm looking at this as a possible way to finally make that move, while keeping the XO in the booth for better monitoring and accessibility.