d858e28d701b553d9b3f02c72ffaa7d5dd4c8729 seems to have messed something up; it's no longer possible to cleanly restart the controller. For some reason, only the Kramer 602 listener seems affected, but after a restart that serial device doesn't communicate with the switcher. Only a full restart of the controller hardware fixes the issue.
d858e28d701b553d9b3f02c72ffaa7d5dd4c8729 is the only relevant change I can see that's happened in that area recently.
Our handling of multiple threads for reading input from devices is pretty horrible anyway and could do with being beaten into order.
There was a reworking of serial comms a while ago - haven't seen this issue since (notwithstanding the fact that we've no longer got that piece of equipment), so I'm going to close this.
d858e28d701b553d9b3f02c72ffaa7d5dd4c8729 seems to have messed something up; it's no longer possible to cleanly restart the controller. For some reason, only the Kramer 602 listener seems affected, but after a restart that serial device doesn't communicate with the switcher. Only a full restart of the controller hardware fixes the issue.
d858e28d701b553d9b3f02c72ffaa7d5dd4c8729 is the only relevant change I can see that's happened in that area recently.
Our handling of multiple threads for reading input from devices is pretty horrible anyway and could do with being beaten into order.