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

Problem with TallyMap.txt #3

Closed
WolliMcBain opened this issue Jan 28, 2025 · 2 comments
Closed

Problem with TallyMap.txt #3

WolliMcBain opened this issue Jan 28, 2025 · 2 comments

Comments

@WolliMcBain
Copy link

Hello.

We work with an ATEM Constellation 8K switcher and 2 PTZ cameras from Birddog (P200). We used the TallyArbiter tool to get the tally control working for each camera individually.

However, as soon as we write 2 lines in the TallyMap.txt, both PTZs turn green or red at the same time. As long as the TallyMap.txt only contains one line, the control works perfectly. We tested it with 2 computers in parallel on which we ran the TallyArbiter and TSL-NDI-Tally. As long as each computer has one line in the TallyMap.txt, everything works fine and both PTZ tallys are controlled correctly. What are we doing wrong?

The TallyMap.txt looks like the following:

1:PTZ2 (CAM)
2:PTZ3 (CAM)

Greetings
Sascha

@iliessens
Copy link
Owner

Hi Sascha,

I haven't used this in a very long time, but you made me curious, so I've tried a similar scenario and am able to reproduce the issue.

I've sniffed the UDP traffic and it seems that TallyArbiter is sending the same tally status on each ID configured in the UI. So, it looks like the issue is on the transmitting side.

This suspicion seems to be confirmed by an existing issue on that repository:
josephdadams/TallyArbiter#765

Not sure a fix will be available for that soon, but it looks like you could use an older version of TallyArbiter as a workaround.

Best regards,
Imre

@WolliMcBain
Copy link
Author

Hi Imre.

First of all, I would like to thank you for your super-fast reply! And thank you for taking the time to recreate our problem!

We downgraded to Arbiter version 3.09 and now everything works perfectly on one computer. We are super happy about the working solution.

Your tool is the only option that offers a solution for small live productions without having to buy expensive hardware. Thank you very much again!

Best regards,
Sascha

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants