• State Not Answered
  • Date
    bsbjuicer
  • Date
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 296 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 were having a lot of errors with wifi remotes. As other wifi devices (such as 5GHz WiFi video transmitters/receivers) would power up, my network would send an error down the line and lock up the main show server. We are usually running a laptop Hog4 PC attached to a DP8000 as the main show "server" with a full size Hog4 hard wired to the network. The laptop outputs Hognet and the full size Hog4 outputs artnet. When using a wireless remote on this system v3.2.0 seemed to be way sensitive to network ups and downs. Hopefully v3.2.1 has improved this. Getting the "client" status back should help some. But it would be nice to have a "client" remote that doesn't kill the whole system if network bandwidth dips for a moment.
Reply
  • 0
    We were having a lot of errors with wifi remotes. As other wifi devices (such as 5GHz WiFi video transmitters/receivers) would power up, my network would send an error down the line and lock up the main show server. We are usually running a laptop Hog4 PC attached to a DP8000 as the main show "server" with a full size Hog4 hard wired to the network. The laptop outputs Hognet and the full size Hog4 outputs artnet. When using a wireless remote on this system v3.2.0 seemed to be way sensitive to network ups and downs. Hopefully v3.2.1 has improved this. Getting the "client" status back should help some. But it would be nice to have a "client" remote that doesn't kill the whole system if network bandwidth dips for a moment.
Children
No Data

www.etcconnect.com