If I could vote for this 10 times, I would. Can’t believe it only had one vote so far.
I am a software/firmware engineer myself, so I don’t mean to trivialize the effort it takes to invoke any new feature into a complex system.
That said, this one seems so obvious and worthwhile that I really can’t believe it wasn’t designed/architected into the system from the start.
Lots of Dante devices I own can be configured to mix control and audio data on the same port.
So I don’t know how everyone else does it, but if A&H’s implementation is physically capable of bridging the two networks (maybe not?), it doesn’t seem like rocket science to send preamp control signals between two boards when one has been put into ‘stagebox mode’.
Even if this control couldn’t (or shouldn’t) be done over the Dante connection, the seems to be very little reason to not make it transparent as long as there’s a ‘normal’ ethernet control connection between the two mixers.
The fact that you can control the ‘slave’ mixer’s gains, etc via iPad is a pretty clear reminder that there is already a bidirectional control protocol in place to remotely change just about anything on a console, including this preamp data. so how much work would it be, really, to use it here?
Granted, as an engineer, that’s exactly the kind of rhetorical question that often gets my hackles up when I get asked it by a sales guy or some upper management type. The answer is often “a lot more work than you think” ;0)
That said, from my safe perch across a nice big ocean, this would seem to be a relatively minor extension of what a console’s UI & communication’s layer is already doing when it ‘knows’ a particular channel is mapped to local IO, DX, DSnake, etc. Namely, “send the relevant UI element’s state to the relevant device using the relevant protocol”.
And you already have the protocol…