-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
Serial tally #682
Comments
Hello there rantwhy 👋 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. |
Sure you just need to use the TSL 3.1 UDP source type in TA. Make sure you are setting it up to listen on whatever port the UDP device is sending. Also remember they must be on the same subnet in order to receive the UDP traffic. |
Hello thank you. I have tried as mentioned above i have even gone to the extent of using a serial debug software and wire shark to make sure the data is getting to the computer running TA. The data is flowing and I can see the ASCII of all the names of the cameras and sources on the switcher but I don not see camera 1 going to program is TA while testing. I just want to confirm that once serial data gets into the IP domain it is just header data and ASCII. TA should not care about the baud rate and parity. only the serial to IP converter just needs to know what it is decoding to send with more or less telnet data. Right? Is there a way to confirm that the data is being interpreted by TA correctly? Is there some way to debug the incoming data stream? Thank you |
Share your TA config file here, maybe we can help. You could also try another Tally testing program. Ross Dashboard has one. |
Hello I am curently using a Ross Vision switcher. I am currently taking the serial tally from the switcher and converting it to UDP with a serial to network converter. I am not sure if this is a acceptable method for TallyArbiter to accept TSL 3.1 As far as I understand that is what the switcher is outputting as far as the serial tally protocol. If there an way to confirm the data is connecting to TA correctly other then the test page? I mean to see the actual data hitting TA. Or is using a serial to network adaptor not correct? Thank you.
The text was updated successfully, but these errors were encountered: