Conceptually, I don't find that very satisfying though: what if you need to combine OSC from multiple sources – eg: object tracking and QLab, and maybe lighting as well? Do you run a piece of software on every OSC source – assuming that you even can (mixing console?) – to echo messages to localhost out to multiple clients? It might work for quite a few specific use cases, but it's not scalable.
How do you switch between redundant sources? I've yet to see an elegant solution for switching OSC: the best so far is to trigger a QLab cue via GPIO-to-MIDI from the changeover button that does KVM & audio, and have that cue somehow work out which machine it's on and set the master overrides accordingly. I don't particularly like that as you rely on the QLab you are switching away from to turn itself off – but why are you switching away from it if it's working well enough to do that? For me, a dual redundant system needs to turn off all output from a device when you're not using it, even if it has crashed.
Wouldn't it be nice to have a separate bombproof router that you could trigger via GPIO that handles all the OSC, just like an XDANTE-1 does for audio?
It's a real shame that when OSC was developed it didn't account for one-to-many (but not all) messaging – unless there is a way of multicasting it (with IGMP snooping of course)?
I wonder if there's a managed switch that can recall presets instantly – so the ports stay on but you allow / deny relevant traffic on the fly? Mirroring would be tricky as the packets need destination address change – is that even a switch function? Something to ponder another day…
Rich