Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: TSL Client reports same state for all devices #765

Open
maklem opened this issue Nov 29, 2024 · 2 comments
Open

[Bug]: TSL Client reports same state for all devices #765

maklem opened this issue Nov 29, 2024 · 2 comments
Assignees
Labels
bug Something isn't working

Comments

@maklem
Copy link

maklem commented Nov 29, 2024

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

{
  "security": {
    "jwt_private_key": "..."
  },
  "users": [
    {
      "username": "producer",
      "password": "...",
      "roles": "producer"
    },
    {
      "username": "admin",
      "password": "...",
      "roles": "admin"
    }
  ],
  "cloud_destinations": [],
  "cloud_keys": [],
  "device_actions": [],
  "device_sources": [],
  "devices": [
    {
      "name": "Cam T0",
      "tslAddress": 0,
      "enabled": true,
      "id": "0cc7e1e2"
    },
    {
      "name": "Cam T1",
      "tslAddress": 1,
      "enabled": true,
      "id": "ec201b8f"
    },
    {
      "name": "Cam T2",
      "tslAddress": 2,
      "enabled": true,
      "id": "b4cc31c3"
    }
  ],
  "sources": [],
  "tsl_clients": [
    {
      "id": "31ca500e",
      "ip": "172.26.240.1",
      "port": 10000,
      "transport": "udp"
    }
  ],
  "tsl_clients_1secupdate": false,
  "bus_options": [
    {
      "id": "e393251c",
      "label": "Preview",
      "type": "preview",
      "color": "#3fe481",
      "priority": 50,
      "visible": true
    },
    {
      "id": "334e4eda",
      "label": "Program",
      "type": "program",
      "color": "#e43f5a",
      "priority": 200,
      "visible": true
    },
    {
      "id": "12c8d699",
      "label": "Aux 1",
      "type": "aux",
      "color": "#0000FF",
      "priority": 100,
      "visible": true
    },
    {
      "id": "0449b0c7",
      "label": "Aux 2",
      "type": "aux",
      "color": "#0000FF",
      "priority": 100,
      "visible": true
    }
  ],
  "externalAddress": "http://0.0.0.0:4455/#/tally",
  "remoteErrorReporting": false,
  "uuid": "59f3ec0f"
}

Relevant log output

No response

Error stacktrace (if applicable)

No response

@maklem maklem added the bug Something isn't working label Nov 29, 2024
Copy link

Hello there maklem 👋

Welcome to TallyArbiter!

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.

@maklem
Copy link
Author

maklem commented Nov 29, 2024

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants