• State Not Answered
  • Date
    bsbjuicer
  • Date
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 300 views
  • Users 0 members are here
Options
Related

3.2.1 vs. 3.2.0

Just wanted to get opinions on v3.2.1 over v3.2.0 I'm stuck on v3.2.0 until the end of my show and can't upgrade. 3.2.0 feels quite jittery on the networking side. I had to give up on wireless remotes because of "lost server" errors locking up the show file. Now all hog devices are hardwired but we still get "server" errors every so often. These are usually corrected by killing and restarting the local board's server and/or desktop. Haven't had this many networking issues on a hog software release in a while and hoping that 3.2.1 has corrected these issues. Any thoughts from the hive mind?

Bryan
Parents
  • 0
    We are usually running 4 stages simultaneously (at one point 6 stages), and sometimes 24 hours a day. The rigging crew has a Roadhog4 as an interface. The 2nd unit uses a RoadHog4 for its unit. I use a Full Size Hog4 and small remote laptop for 1st unit. We are constantly moving from stage to stage so it is nice to have a "show server" that is linked to a particular stage/set. Each crew just has to log in to the show file and work. If the operators are not there, the dimmer techs can bring up a work light look off the server for the other crews. It would be nice to have 7 full size Hogs, but not economically feasible.

    I'm just probing to see if it is possible for the client/server relationship between hogs to be more robust. If the server loses a client for a moment (less than a second), then it should reconnect and continue like nothing happened. It should not cause a full restart of the system as it does many times.

    Bryan
Reply
  • 0
    We are usually running 4 stages simultaneously (at one point 6 stages), and sometimes 24 hours a day. The rigging crew has a Roadhog4 as an interface. The 2nd unit uses a RoadHog4 for its unit. I use a Full Size Hog4 and small remote laptop for 1st unit. We are constantly moving from stage to stage so it is nice to have a "show server" that is linked to a particular stage/set. Each crew just has to log in to the show file and work. If the operators are not there, the dimmer techs can bring up a work light look off the server for the other crews. It would be nice to have 7 full size Hogs, but not economically feasible.

    I'm just probing to see if it is possible for the client/server relationship between hogs to be more robust. If the server loses a client for a moment (less than a second), then it should reconnect and continue like nothing happened. It should not cause a full restart of the system as it does many times.

    Bryan
Children
No Data

www.etcconnect.com