Re: #thatfeeling
Any time a remote function causes the audio to be disrupted or the console functions to be disabled is a huge design flaw. The old Presonus that required a Firewire connection for remote control. The problem was, if the host computer would be disconnected, or even restarted, the audio would drop on the Presonus. While it was only a couple seconds, it meant the reliability of audio was tied to 100% reliability of the external computer. As we know, computers can crash, unexpectedly at times. Because of this, I ended up abandoning having the computer connected at all during shows.
A properly designed system should be able to deal with corrupted data packets for remote control functionality. It's understandable if the actual audio stream is corrupted that there would be interruption in sound, but if the console can be crashed, that's poor programming. On the Soundcraft boards, I have heard of this happening more than on any other console. On other consoles (Yamaha, behringer, etc) there are issues with remote control that simply make the remote control unresponsive. Yes, it's a problem if that's your ONLY way to mix, but with every failure I've seen, the solution is simply return to the console and mix from there. Yes, it sucks if you're across the room at the time, but if you have to run back to the console and then wait for it to reboot when you get there, that makes for a very bad day.