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
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: