You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting in version 3.1.0 the module for TSL-clients sends the same status for all devices.
I expected the status sent via TSL to match the one in the UI.
Version
3.1.0, 3.1.1
Distribution
Desktop
OS
Windows
What browsers are you seeing the problem on?
No response
If applicable, What Listener Clients are You Using?
Thank you for opening your first issue for the Tally Arbiter project. Tally Arbiter fosters an open and welcoming environment for all our contributors. Please adhere to our Code Of Conduct.
If you have more to contribute to this issue, please comment down below! We will try to get back to you as soon as we can.
As far as I have figured out the TSL module receives currentDeviceTallyData, which was updated from currentSourceTallyData in index.ts:1238. As far as I can see only the sourceId is taken into account, but not an address. From my understanding the address is needed to distinguish different channels within a source (i.e. TEST Mode source).
What happened?
Starting in version 3.1.0 the module for TSL-clients sends the same status for all devices.
I expected the status sent via TSL to match the one in the UI.
Version
3.1.0, 3.1.1
Distribution
Desktop
OS
Windows
What browsers are you seeing the problem on?
No response
If applicable, What Listener Clients are You Using?
No response
TallyArbiter configuration
Relevant log output
No response
Error stacktrace (if applicable)
No response
The text was updated successfully, but these errors were encountered: