Hi,
Eos v1.9.11, aRFR v1.0.1 r15
Is the 5min timeout (300000ms) a new thing?
We've had the aRFR disconnect (looking at the logs forcabley by the desk) while focusing a lantern for over 5mins or with the LD using the "cues" tab to see the current cue in a dress.
When focusing it's a bit annoying as when using chancheck the selected channel goto 0, and if using live you have to change back to that tab and reselect the channel.
The eos logs show: "RFR inactivity timeout (300014ms elapsed)"
To me it seems odd for the onyx/eos to manage a timeout on a TCP connection, surely this can be done at a winsock level?
Marcus
