Hi, It is snesibly fixture patch on dp 1and the same patch on dp2 for backup when dp 1 chrashed?switch of dp2 with dmx lines.when the console chrased is end.or is it not good idea.
Crashes on the DPs themselves are rare these days and by creating a redundant patch on DP2 you are not protecting again the more commonly seen issues which usually occur on the console in the desktop or server process. I would recommend using Midi Show Control to track playback from your main console running one DP to a second console or Hog3PC setup running the other DP. This ensures an isolated backup and will protect you from being left in the dark since the second desk is isolated and not effected by crashes on the main desk.
Hello- See if this tutorial will help you out: How to Setup a Backup Console Using Midi Show Control
This document uses a Wholehog 3 console as the server and a Hog3PC with a widget as an example - but the MSC setup is the same regardless of what Hog console hardware you use.
OK, from what I'm getting, if you do an MSC control, its only triggering a copy of a premade show" -- half or more of my crashes occur when I'm live changing something, say an efx or position and UPDATE or something ... things like that wouldn't go over MSC would they? Networking hasn't really done the trick with me either since it's usually the console running server that crashes (I'd run the show server and program on my H3 with iPC connected as console2) -- I've also tried it backwards, running the iPC as the server, using my H3 as console 2, no server running, and the response time is less than steller ...
Just trying to come up with better solutions if I'm missing something.
If you use MSC and one of your desk crashes, the other one is not gonna get affected whatsoever. When working with networking server desk should be left basically doing nothing. Slaves are the ones you should program on and if you do something that crashes the desk , al least your Show is safe since your server is still up and running. We're all looking forward to slave desks being able to take over a show in case the server dies. Marco:hogsign:
You are correct. Updates to the show file are not transmitted to the backup desk over MSC. The midi show control backup solution works best in cases where you're changes to the show are completed before curtain and you can then load duplicate copies of the show on two different desks and have the backup track the main console via MSC.
