[Bug]: TSL3.1 Listener Output Preview/Program Tally Inverted

[lestrobl]

What happened?

It seems, that the TSL3.1 UDP Output sends inverted tallys (preview/program)

Version

3.10

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

No response

Relevant log output

No response

Error stacktrace (if applicable)

No response

[github-actions]

Hello there lestrobl 👋

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.

[josephdadams]

The device action? Or the tsl clients area

[lestrobl]

TSL Clients under "Listeners"

Also a Videosys telemtetry unit reported inverted states (Green Tally on Program, Red Tally on Preview)

[josephdadams]

I wonder if it could be an issue with your configuration. I use the TSL clients area regularly without issue, and I can tell you that on a code level, the outgoing TSL object is created without regard to the transport type (udp, tcp) and then it is sent accordingly. Which means I would expect to see it inverted in my setup which is using TCP.

[josephdadams]

Can you post your config file?

[lestrobl]

Of course:
config.json

It even happened on a fresh install using only the test mode.
I only tested TSL3.1UDP

[Christoph111]

hi, i can confirm that! i configured my skaarhoj controller and was wondering why everything was triggered inverted...can you provide a quik fix and swap the bits?

[Jocke4f]

I don't understand if this is a fault or a configuration issue. In TSL v3.1 4 tallies are defined.

In TA the tallies are mapped like this in the TSL RunAction:

• Tally 1 - PVW
• Tally 2 - Program.

Source: https://tslproducts.com/media/1959/tsl-umd-protocol.pdf

TallyView for TSL UMD (v1.2) uses red for Tally 1 and green for Tally 2. Since red is normally understood as program and and green as preview does it look as a mismatch, atleast is it confusing.

There is other online documentation for ROSS Carbonite that supports the TA implemenation. see https://help.rossvideo.com/carbonite-device/Topics/Devices/UMD/TSL.html

I can't based on the TSL v3.1 standard determine if TA or the viewer is wrong.

NB: It is possible to circumvent this issue by instead selecting Tally 2 (PGM) for Preview and Tally 1 (PVW) for Program in the RunAction setup in TA.

[Christoph111]

NB: It is possible to circumvent this issue by instead selecting Tally 2 (PGM) for Preview and Tally 1 (PVW) for Program in the RunAction setup in TA.

hey, what exactly do you mean by this? how to do this?

[Jocke4f]

In the TSL 3.1 protocol 4 tallies are defined, it is not defined which tally is what. It is implementation dependant if 1 or 2 is mapped to Preview or Program. The suggestion in TA is:

• Tally 1 - PVW is suggested
• Tally 2 - Program is suggested
• Tally 3 - No suggestion.
• Tally 4 - No suggestion.

This is the same as the implementation in ROSS Carbonite.

If your device has a different implementation e.g. Tally 1 is Program and Tally 2 is Preview then this is configured in the Action.

Given this, if your device implements Tally 1 as Program and Tally 2 as Preview than you have to connect Program with Tally 1 and Preview with Tally 2.

This gives the following result.

Perhaps it would be less confusing is the (PVW) and (PGM) was not present in the UI for Actions but on the other hand is it correct when using a ROSS Carbonite.

I hope this explains why this is not it considered a bug.

[josephdadams]

I vote that we remove the PVW and PGM from the UI as suggested.

[Jocke4f]

I have removed PVW and PGM from the UI. The challenge remains when configuring a TSL Clients on the Listener page since in that case Preview is hardcoded as Tally 1 and Program as Tally 2. Perhaps it should be possible to configure this per added TSL client.